Skip to content
Pulumi MCP Server

Pulumi MCP Server

by Pulumi
Added to Onei
v0.2.0
Repository Docs npm
Cloud & Infrastructure

Summary

Pulumi's official MCP server: search your Pulumi Cloud resources, read the provider registry while generating infrastructure code, and delegate work to the Pulumi Neo agent.

Features

  • Pulumi Cloud queries: get-stacks, resource-search, get-policy-violations, get-users
  • Provider registry lookups so generated code uses real resource and function schemas
  • deploy-to-aws for pushing a generated program out
  • Delegation to the Pulumi Neo agent with task tracking and continuation
  • Remote HTTP endpoint at mcp.ai.pulumi.com/mcp, or a local stdio server on npm

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Pulumi MCP Server" tools will be available.
{
  "mcpServers": {
    "pulumi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.ai.pulumi.com/mcp"
      ]
    }
  }
}

Description

Infrastructure-as-code is one of the places where an LLM writing from memory goes wrong quietly — provider resource schemas change, and a plausible-looking property name simply fails at deploy time. The Pulumi MCP server addresses that by giving the assistant the registry itself, plus a live view of what is actually deployed in your Pulumi Cloud organisation.

Three groups of tools

Pulumi Cloud — get-stacks, resource-search, get-policy-violations and get-users let an agent answer questions about the estate you already run: which stacks exist, where a given resource lives, what policy is currently being violated, and who has access.

Registry and deployment — get-type, get-resource, get-function, list-resources, list-functions and deploy-to-aws let the agent look up real provider schemas while writing a program rather than guessing at them, and push a result to AWS.

Neo delegation — neo-bridge, neo-get-tasks, neo-continue-task and neo-reset-conversation hand a task to Pulumi Neo, Pulumi's own infrastructure agent, and then track or continue it from your assistant. This is the more unusual capability: rather than doing the work in-context, the MCP server becomes a bridge to a specialised agent that owns the change.

Setup

The current path is the remote HTTP server. In Cursor, add a pulumi entry to .cursor/mcp.json with "transport": "http" and the URL https://mcp.ai.pulumi.com/mcp. Claude Desktop and Kiro, which expect a local process, reach the same endpoint through npx mcp-remote. A local stdio implementation is also published on npm as @pulumi/mcp-server.

Who it is for

Platform and infrastructure teams already on Pulumi who want an assistant that writes against accurate provider schemas, can answer questions about the live estate, and can escalate a change to Neo rather than pretending to apply it.

Related MCP Servers

See all Pulumi MCP Server alternatives

MCP: Terraform

by HashiCorp

HashiCorp's official MCP server for the Terraform Registry, HCP Terraform and Terraform Enterprise — providers, modules, policies and workspace operations.

Cloud & Infrastructure

MCP: AWS MCP Server

by Amazon Web Services

Featured

AWS's managed MCP server: call any AWS API, run sandboxed Python against your account, and load AWS agent skills on demand — under IAM, CloudWatch and CloudTrail.

Cloud & Infrastructure

MCP: Vantage MCP Server

by Vantage

Official Vantage MCP server: ask an AI assistant about your cloud costs, usage, tagging and budgets across AWS, Azure, GCP and more — hosted with OAuth or self-hosted via npx.

Cloud & Infrastructure
Browse all MCP servers →