Pulumi MCP. Audit, track, and manage your cloud state via conversation.
Pulumi connects your agent directly to your infrastructure state. Use this MCP to list organizations, manage stacks (create, delete), track deployment history, inspect outputs like IPs and URLs, and add tags—all via natural conversation.
Give Claude and any AI agent real-world access
The MCP allows you to list all stacks within an organization, giving you a quick map of your deployed environments.
You can review the full stack update history for any project, seeing which resources changed and who triggered the deployment.
Get specific information about a stack or organization, such as member lists or key configuration settings.
Fetch critical values from the latest deployment, including API URLs, IP addresses, and resource IDs needed for other services.
Set or list custom tags on stacks (like environment=prod or team=platform) to keep your infrastructure organized and searchable.
Ask an AI about this
Waiting for input…
What AI agents can do with Pulumi: 11 Tools for Infrastructure Ops
Use these tools to manage the entire lifecycle of your cloud infrastructure, from listing environments to retrieving live resource details.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Pulumi MCPCreate Stack
This tool creates a new, isolated instance of your infrastructure program for testing or staging environments.
Delete Stack
It permanently deletes an entire stack and all resources associated with it. Use...
Get Current User
This tool verifies your identity by retrieving the GitHub login, email, and avatar...
Get Deployment
Retrieves specific details about a single deployment using its version number and...
Get Organization
Fetches high-level information and settings for an entire Pulumi organization by its...
Get Stack Outputs
This tool collects all values your program exported during the last deployment, such as URLs or resource IDs.
Get Stack
Provides detailed information about a specific stack, including its status and core configuration.
List Deployments
You can see the complete history of deployments for a stack, tracking who ran it and...
List Stack Tags
Lists all key-value metadata labels currently applied to a specific stack.
List Stacks
Retrieves a list of every isolated stack within your Pulumi organization, showing...
Set Stack Tag
This tool applies or updates organizational tags (like setting the environment to...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Pulumi, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Pulumi. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Checking Infrastructure Status is a Time Sink
Right now, checking if your staging environment stack is ready means logging into multiple web consoles. You click on the 'Stacks' tab to see names, then you click on a specific name to check status, and finally, you might have to navigate three different tabs—History, Outputs, Tags—just to gather a single picture of what happened.
With this MCP, your agent does all that work for you. You just ask: 'What's the status of the staging stack?' And the system aggregates the deployment history, current outputs, and resource count into one clean response. It's immediate context.
Pulumi MCP Gives You Total State Visibility
The manual steps that vanish include opening tabs to check tags, switching windows to view deployment logs, and manually copying endpoints from the output page. These are all repetitive tasks with zero value-add.
Now, your agent combines these checks into one conversation. You get a single, comprehensive answer about resource provisioning and status. It’s not just faster; it changes how you operate.
What Pulumi MCP does for your AI
You can connect your agent to Pulumi and take full control of your cloud infrastructure from a chat window. Instead of logging into the console to check status or grab an endpoint URL, you just ask for it. Your AI client acts like a dedicated DevOps engineer right in your chat interface, giving you immediate visibility into everything.
Need to know which stacks exist? You can list them instantly. Did the last deployment succeed? Check the history and see exactly what changed. The power of Vinkius makes this possible; your agent accesses this full catalog of infrastructure tools so you don't have to switch context or copy-paste commands anymore.
019d8472-4ff7-720c-8caf-a89c8ea7eb7f How to set up Pulumi MCP
The bottom line is you get to manage complex cloud operations using simple conversation instead of clicking through multiple dashboards.
First, subscribe to the Pulumi MCP on Vinkius and enter your Pulumi Access Token.
Second, prompt your agent with a natural language request (e.g., 'Show me all dev stacks in the finance project').
Third, your AI client executes the necessary tool calls and returns structured data—like stack names or deployment status—directly into the chat.
Who uses Pulumi MCP
This MCP is for platform engineers and DevOps specialists who are tired of context switching. If your job involves checking deployment status, auditing resources, or finding a specific endpoint URL after a build, this saves you hours of repetitive clicking.
Uses the MCP to audit resource changes and track deployment success/failure patterns without opening the Pulumi console.
Manages stack tags across multiple organizations, ensuring environments are correctly categorized for cost-center tracking or compliance audits.
Requests exported endpoints and connection strings from the latest deployment to integrate into local development code.
Benefits of connecting Pulumi MCP
Stop jumping between tabs. You can list all stacks or audit deployment history instantly by asking your agent, eliminating manual dashboard checks.
Never lose an endpoint URL again. Use the MCP to get_stack_outputs and pull critical IPs, URLs, and connection strings from any successful deployment in one go.
Keep track of who did what and when. Reviewing the full stack update history via list_deployments gives you a non-repudiable audit trail for compliance or debugging.
Better organization means better governance. You can use set_stack_tag to apply mandatory metadata (like cost centers) across dozens of environments at once.
Get context fast. Instead of digging into documentation, simply ask the MCP to get_organization details and immediately understand your infrastructure scope.
Pulumi MCP use cases
Debugging a failed deployment
A developer notices an endpoint is down. They ask their agent to list_deployments for the 'api' stack, find the failure version, and then use get_stack_outputs to see what resources were provisioned right before the crash.
Onboarding a new team member
A platform architect needs to show a new hire all available environments. They simply ask the agent to list_stacks, which returns every stack name and its last update time without needing manual navigation through project folders.
Preparing for compliance audit
The ops engineer must prove that all production stacks are correctly tagged. They use list_stack_tags to confirm tags like 'environment=prod' and then set_stack_tag if any critical tag is missing.
Finding a database connection string
A backend developer needs the DB endpoint for staging. Instead of querying the console, they ask the agent to get_stack_outputs on the 'staging' stack and instantly receive the required db_endpoint.
Pulumi MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Manual Console Checking
A user has to log into the Pulumi web console, navigate to the specific project, select the correct stack, and then click 'History' to see a timeline of changes.
Instead, ask your agent to list_deployments or get_stack for the target environment. The MCP pulls that audit data directly without you ever opening the dedicated web console.
Copying Outputs
After a successful deployment, a user manually navigates to the 'Outputs' tab and copies five different URLs or resource IDs into a spreadsheet.
Ask your agent to get_stack_outputs. The MCP collects all exported values—URLs, IPs, etc.—and presents them cleanly for immediate use.
Forgetting Organization Scope
A user is unsure if a stack belongs to the 'finance' or 'hr' project and opens multiple console tabs trying to locate it.
First, run list_stacks. This tool shows every stack in your entire organization, giving you instant visibility into which team owns what.
When to use Pulumi MCP
Use this MCP if your job requires programmatic interaction with the state of deployed cloud infrastructure. Specifically, if you need to audit history (list_deployments), manage metadata (set_stack_tag), or retrieve runtime data (get_stack_outputs) without manual clicking, this is for you. Don't use it if your goal is simply writing the initial code; that requires a dedicated IaC editor. Also, don't use it if you just need to list resources in an IDE—that's better handled by type-safe validation tools. This MCP handles the state and history; it doesn't write the code itself.
Frequently asked questions about Pulumi MCP
How do I check if my Pulumi stack is configured correctly using the Pulumi MCP? +
You use list_stack_tags to see what metadata labels are applied. You can also get_organization details to verify settings at the top level.
Can I find out which user ran a specific deployment on my stack using Pulumi MCP? +
Yes, list_deployments shows the full history for your stack and includes the name of the user who triggered each deployment event.
What is the difference between get_stack and get_organization in the Pulumi MCP? +
get_organization provides details about the top-level container (the whole company setup), while get_stack gives you granular info on one isolated environment within that organization.
Does the Pulumi MCP let me create a new infrastructure stack? +
Yes, the create_stack tool allows your agent to provision a brand-new, isolated instance of your infrastructure program for testing or staging use.
How do I retrieve exposed URLs from my deployed services using Pulumi MCP? +
You call get_stack_outputs. This tool collects all values the code exported during deployment, including IPs and external-facing URLs.