RELATED 01
Pulumi MCP Server
OFFICIAL SERVERLocal Pulumi server that looks up registry schemas and runs preview, up and refresh on your stacks
8.9k/wknpm downloads
20popularity score
Pulumi MCP Server
Pulumi's hosted MCP endpoint for stacks, resource search, registry schemas and Neo tasks
Official · pulumi.com Remote (hosted) · Streamable HTTP Cloud platformsDevOps and monitoring
Connect your client
Remote (hosted)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude CodeTerminal
claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcpClaude (desktop and web)Settings → Connectors → Add custom connector
https://mcp.ai.pulumi.com/mcpChatGPTSettings → Apps → Advanced → Developer mode, then Create app
https://mcp.ai.pulumi.com/mcpCursor~/.cursor/mcp.json
{
"mcpServers": {
"pulumi": {
"url": "https://mcp.ai.pulumi.com/mcp"
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"pulumi": {
"type": "http",
"url": "https://mcp.ai.pulumi.com/mcp"
}
}
}Codex~/.codex/config.toml
[mcp_servers.pulumi]
url = "https://mcp.ai.pulumi.com/mcp"Gemini CLITerminal
gemini mcp add --scope user --transport http pulumi https://mcp.ai.pulumi.com/mcpWhat it does
This is the MCP server Pulumi runs itself at https://mcp.ai.pulumi.com/mcp. Nothing is installed locally: a client connects over streamable HTTP and every call goes to Pulumi Cloud under the identity of a Pulumi access token you supply.
Its 14 tools fall into four groups. Pulumi Cloud tools list the stacks, members and policy-as-code violations in an organization and run resource search queries across all stacks (for example, every resource from the aws package, or resources missing tags). Registry tools look up provider resource types, functions, properties and type schemas, which helps an assistant write correct Pulumi code. Neo tools start Pulumi Neo tasks, send follow-ups and approvals, list tasks and read their progress. A deploy-to-aws tool returns instructions the assistant follows to write a Pulumi program for an existing app. It also offers six prompts, including Terraform-to-TypeScript conversion and several AWS CDK migration guides.
Per Pulumi's docs the server itself never runs pulumi up and most tools only read; changes to infrastructure happen only through Neo, when a Neo request is approved. This differs from Pulumi's older local package @pulumi/mcp-server (version 0.2.0 on npm), whose tools include pulumi-cli-preview and pulumi-cli-up and drive the Pulumi CLI on your own machine; the hosted server has no CLI tools and different tool names.
What it needs
A Pulumi Cloud account and a Pulumi access token (personal, or an organization token on Essentials, Pro or Enterprise). resource-search and neo-bridge need an Essentials, Pro or Enterprise edition, and Neo must be enabled for the organization. A client that supports remote MCP over streamable HTTP with OAuth; stdio-only clients can bridge through the mcp-remote package, which needs Node.js. In Claude Code, finish sign-in by running /mcp and authenticating in the browser.
Limits
Browser sign-in sessions last 30 days, then the client must authenticate again; a deleted or expired token makes calls fail until you re-authenticate. With header sign-in, a missing or inaccessible X-Pulumi-Org silently falls back to the first organization the token can reach, without an error. neo-bridge costs money: each task, message or approval counts against the organization's Neo usage. Some clients, including Cursor, cache tool lists and need a restart to see new tools. It cannot run Pulumi CLI operations such as preview or up itself.
Who it suits
Suits teams already on Pulumi Cloud who want an assistant to inspect stacks, find untagged or drifting resources, check policy violations, or look up registry schemas while writing Pulumi code, without installing anything. An organization token with a read-only role plus a deny rule on neo-bridge keeps it read-only. Pick something else if you have no Pulumi Cloud account, need everything to run on your own machine, or want the assistant to run pulumi preview and up directly: Pulumi's local @pulumi/mcp-server package drives the CLI instead.
Tools 14
get-stacks- Lists the organization's stacks.
resource-search- Runs a resource search query across all stacks.
get-policy-violations- Lists policy-as-code violations on the stacks.
get-users- Lists organization members with their roles.
neo-bridge- Starts a Neo task, sends follow-ups, and approves or rejects its requests (billed).
neo-get-tasks- Lists the organization's Neo tasks and their state.
neo-continue-task- Reads the status and recent events of an existing Neo task.
neo-reset-conversation- Clears the server's tracked state for one or all Neo tasks.
list-resources- Lists resource types in a registry provider or module.
list-functions- Lists functions in a registry provider or module.
get-resource- Returns a resource type's properties and docs.
get-function- Returns a function's inputs, outputs and docs.
get-type- Returns the JSON schema for a type reference.
deploy-to-aws- Returns steps for writing a Pulumi program that deploys an app to AWS.