Pulumi MCP Server
OfficialGive agents Pulumi powers: browse the provider registry, preview and deploy stacks, and search deployed resources.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx @pulumi/mcp-server@latest stdioPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"pulumi-mcp-server": {
"command": "npx",
"args": [
"@pulumi/mcp-server@latest",
"stdio"
]
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Pulumi CLI installed on the client machine (required for preview/up/refresh operations)
- Node.js with npx, or Docker for the containerized mode
- A Pulumi access token (app.pulumi.com/account/tokens) for Docker mode and the hosted endpoint; registry tools work without credentials
About Pulumi MCP Server
Pulumi's MCP server targets the full infrastructure-as-code loop rather than just documentation lookup. The registry tools (pulumi-registry-list-resources, -get-resource, -get-function, -get-type) let an agent discover what a provider offers and fetch exact schemas and code examples — which is what stops LLMs from inventing resource properties when writing Pulumi programs. The CLI tools then close the loop: preview a change, deploy it, read stack outputs, or refresh state to detect drift.
pulumi-resource-search queries your deployed infrastructure across cloud providers ('how many S3 buckets do we have?'), and neo-task-launcher hands bigger jobs to Pulumi Neo, the company's infrastructure agent. A deploy-to-aws prompt provides guided deployment workflows.
Deployment options are layered: local stdio via npx (needs Node plus the Pulumi CLI for stack operations), Docker (mcp/pulumi image, with PULUMI_ACCESS_TOKEN env and a volume mount when the CLI needs your project files), or Pulumi's hosted remote MCP at mcp.ai.pulumi.com/mcp using HTTP transport — the current recommendation in Pulumi's docs, with mcp-remote bridging for stdio-only clients like Claude Desktop.
One housekeeping note: the standalone pulumi/mcp-server GitHub repo now 404s (the code appears to have moved into Pulumi's monorepo structure), so the npm page and Pulumi's docs are the canonical references. The package remains actively published by Pulumi.
Tools & capabilities (11)
pulumi-registry-list-resourcesBrowse available cloud resources across providers.
pulumi-registry-list-functionsExplore available provider functions.
pulumi-registry-get-resourceGet code examples and documentation for a specific resource.
pulumi-registry-get-functionGet provider function examples for your Pulumi program.
pulumi-registry-get-typeGet schema definitions for complex resource properties and types.
pulumi-cli-previewPreview infrastructure changes before deployment.
pulumi-cli-upDeploy infrastructure changes, creating and updating resources.
pulumi-cli-stack-outputRetrieve stack outputs like URLs and resource IDs.
pulumi-cli-refreshSync Pulumi state with actual cloud resources to detect drift.
pulumi-resource-searchDiscover, count, and analyze deployed infrastructure across cloud providers.
neo-task-launcherHand tasks to Pulumi Neo for advanced infrastructure work.
What this server can do
Pulumi MCP Server provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Write correct Pulumi programs with real provider schemas instead of hallucinated properties
- Preview and deploy a stack change from a coding agent, with outputs read back
- Audit deployed infrastructure: count resources, find drift via refresh
- Guided deploy-to-AWS workflows using the built-in prompt
Quick setup
- 1Install the Pulumi CLI and log in (pulumi login)
- 2Claude Code: claude mcp add -s user pulumi -- npx @pulumi/mcp-server@latest stdio
- 3Claude Desktop: add {"command": "npx", "args": ["@pulumi/mcp-server@latest", "stdio"]} under mcpServers
- 4Docker alternative: docker run -i --rm -e PULUMI_ACCESS_TOKEN=<token> -v ~/projects/my-app:/app/project mcp/pulumi:latest stdio
- 5Hosted alternative: claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcp
Security notes
pulumi-cli-up deploys real infrastructure with your Pulumi credentials — keep previews auto-approved at most, and gate up/refresh behind human review. Tokens: the Docker mode takes PULUMI_ACCESS_TOKEN as an env var, and the hosted endpoint authenticates with a Pulumi access token from app.pulumi.com/account/tokens.
Pulumi MCP Server FAQ
Is the Pulumi MCP server safe to let an agent use?
Registry and preview tools are read-only and low-risk; pulumi-cli-up and refresh change real cloud infrastructure using your Pulumi credentials, so keep them behind manual approval. The server itself is official Pulumi software distributed via npm and Docker.
Where did the GitHub repo go?
pulumi/mcp-server now returns 404 — the code moved as Pulumi consolidated repos. The npm package @pulumi/mcp-server is still actively published by Pulumi, and the docs page at pulumi.com/docs/iac/using-pulumi/mcp-server is the maintained reference.
Local stdio or hosted endpoint — which should I use?
Use local stdio (npx @pulumi/mcp-server@latest stdio) when the agent needs your local project files and CLI login for preview/up. Use the hosted https://mcp.ai.pulumi.com/mcp endpoint for registry, resource search, and Neo features from HTTP-capable clients, authenticating with a Pulumi access token.
Alternatives to Pulumi MCP Server
Compare all alternatives →GitHub's official server for repos, issues, PRs, and Actions — local Docker or hosted remote.
Official AWS Labs server that lets agents call any AWS API via the AWS CLI surface.
Bulk Kubernetes port forwarding with an MCP server that lets AI assistants forward services, inspect pods, and monitor traffic.
Compare Pulumi MCP Server with: