Integrate Pulumi with Claude, Cursor, Chatbots & AI Agents MCP Server

Q: Can I view the outputs of a stack?

Yes! Use getstackoutputs with the org name, project name and stack name. It returns all exported output values from the latest successful deployment, such as URLs, IP addresses, resource IDs and connection strings. This is useful for discovering endpoint addresses after infrastructure deployment.

Manage cloud infrastructure via Pulumi — list stacks, track deployments, audit outputs and tag resources from any AI agent.

GDPR Free for Subscribers

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

create

Create stack on Pulumi

A stack is an isolated, independently configurable instance of your Pulumi program. Requires the org name, project name and stack name (e.g. "staging", "prod"). Returns the created stack with its URL. Create a new Pulumi stack

delete

Delete stack on Pulumi

The stack must be empty (no resources) or force deletion must be enabled. Provide the org name, project name and stack name. WARNING: this action is irreversible. Delete a Pulumi stack

get

Get current user on Pulumi

Returns the user's GitHub login, avatar URL, email and name. Use this to verify your access token is working correctly and to see which identity the API calls will appear as. Get the currently authenticated Pulumi user

get

Get deployment on Pulumi

Provide the org name, project name, stack name and deployment version number. Get details for a specific Pulumi deployment

get

Get organization on Pulumi

Provide the organization name (slug). Get details for a specific Pulumi organization

get

Get stack on Pulumi

Provide the org name, project name and stack name. Get details for a specific Pulumi stack

get

Get stack outputs on Pulumi

Outputs are values your Pulumi program exports, such as URLs, IP addresses, resource IDs and connection strings. Useful for discovering endpoint addresses and configuration values after infrastructure deployment. Get the exported output values from a Pulumi stack

list

List deployments on Pulumi

Each deployment shows its version number, status (succeeded, failed, in-progress), start/end time, resource changes (created, updated, deleted) and the user who triggered it. Use this to audit infrastructure changes and track deployment success/failure patterns. List deployment history for a Pulumi stack

list

List stack tags on Pulumi

Tags are key-value metadata labels used for organizing, filtering and managing stacks (e.g. environment=prod, team=platform, cost-center=engineering). List tags on a Pulumi stack

list

List stacks on Pulumi

Each stack represents an isolated, independently configurable instance of your infrastructure (e.g. dev, staging, prod). Returns stack name, project name, last update info, resource count and whether updates are in progress. List all stacks in a Pulumi organization

set

Set stack tag on Pulumi

Tags are used for organizing, filtering and managing stacks (e.g. key="environment", value="prod", key="team", value="platform"). Provide the org name, project name, stack name, tag name and tag value. Set a tag on a Pulumi stack

Security & Code Integrity Audit

Every tool in the Pulumi MCP Server is continuously audited by the Vinkius Security Engine. We guarantee zero-trust payload isolation, strict data boundaries, and deterministic execution for enterprise-grade AI agents.

A+Score: 98.33

How Vinkius protects your data

Can I set different limits for each virtual assistant on my team?

Absolutely. You have full control in our command center. You can create an AI agent that only "reads" data so the support team can answer questions, and another superpowered agent that can "edit" and "create" information exclusively for your operations team. Each AI gets exactly the level of access you allow.

Can I view the outputs of a stack?

Yes! Use get_stack_outputs with the org name, project name and stack name. It returns all exported output values from the latest successful deployment, such as URLs, IP addresses, resource IDs and connection strings. This is useful for discovering endpoint addresses after infrastructure deployment.

How does the AI access my passwords and credentials?

It simply doesn't. On Vinkius, your passwords, API keys, and login details are kept in a secure vault. The AI (like ChatGPT or Claude) merely "asks" Vinkius to perform the task. Vinkius opens the door, does the work, and hands the result back to the AI. Your credentials are never seen, read, or learned by the artificial intelligence.

What happens if the underlying API rate limits my agent?

Our edge infrastructure automatically handles backoffs, queueing, and throttling. If an AI agent sends too many erratic requests, Vinkius manages the rate limits gracefully, ensuring your backend doesn't crash.

Supported Use Cases for Pulumi

Build automated workflows with Cursor and Claude Code by connecting to the Pulumi MCP server.

Streamlining infrastructure as code

Connect Pulumi to your AI agents (Claude, ChatGPT, Cursor) to manage infrastructure as code operations. The MCP server processes the underlying API requests and schema formatting for the loved by devs domain.

LLM Orchestration for cloud deployment

The Pulumi server exposes documented endpoints for cloud deployment. This allows ChatGPT and Cursor to interact with loved by devs APIs seamlessly.