Hosting

Remote, hosted

Transport

Streamable HTTP

Endpoint

https://mcp.ai.pulumi.com/mcp

Authentication

Initial browser flow asks for a Pulumi access token and default organization; session lasts 30 days. Headless clients may send Authorization: Bearer ${PULUMI_MCP_TOKEN} and X-Pulumi-Org headers. A separate MCP token is recommended; use least privilege.

Requirements

• Pulumi Cloud token and an organization for cloud tools.
• Some features require specific Pulumi Cloud editions: resource-search and Neo tools have edition/usage constraints; Neo usage is billed.
• Client supporting remote Streamable HTTP with OAuth, or stdio-only client bridged with mcp-remote and Node.js.

Setup steps

1. Add https://mcp.ai.pulumi.com/mcp as a remote MCP server.
2. On first connection, authenticate with a Pulumi access token, select the default organization, review the redirect URL, and authorize.
3. Use an organization-scoped token with least privilege where possible; deny `neo-bridge` if you do not want task delegation.
4. Start with a read-only request such as listing stacks or looking up a Registry resource schema.
5. Reconnect to switch organizations; reauthenticate when the 30-day session expires.

Pulumi’s current tool table contains the 14 stored tool identifiers. The separate prompt catalog is not included in the MCP tool count. Neo actions can consume usage and can lead to infrastructure changes when approved.

• get-stacks

  List stacks in the organization.

  01
• resource-search

  Search resources across stacks.

  02
• get-policy-violations

  List policy-as-code violations.

  03
• get-users

  List organization members and roles.

  04
• neo-bridge

  Start a Neo task, send messages, and approve or reject requests; may incur usage and enable changes.

  05
• neo-get-tasks

  List organization Neo tasks and status.

  06
• neo-continue-task

  Check a Neo task and read latest events.

  07
• neo-reset-conversation

  Clear tracked state for a task or all tasks.

  08
• list-resources

  List resource types in a provider or module.

  09
• list-functions

  List functions in a provider or module.

  10
• get-resource

  Get resource properties and documentation.

  11
• get-function

  Get function inputs, outputs, and documentation.

  12
• get-type

  Get the JSON schema for a type reference.

  13
• deploy-to-aws

  Provide instructions for the agent to analyze an application and write Pulumi code to deploy it to AWS.

  14

• Most tools are read-only, but `neo-bridge` can start billed work and may allow infrastructure changes or pull requests after approval.
• Resource search and Neo require eligible editions; Neo usage is billed.
• Access follows token identity and organization RBAC.
• Some clients cache definitions; restart or reconnect when renamed tools do not appear.

• official tool reference

  Current Pulumi tool reference enumerates all 14 stored tool names across Pulumi Cloud, Neo, Registry and AWS code generation; prompts are separate from tools. Neo task creation/approval can incur usage and may change infrastructure.

• official documentation or source

  Current Pulumi tool reference enumerates all 14 stored tool names across Pulumi Cloud, Neo, Registry and AWS code generation; prompts are separate from tools. Neo task creation/approval can incur usage and may change infrastructure.

Documentation checked 2026-10-28T13:00:03.000Z. Connection has not been runtime tested.