Hosting

both

Transport

Streamable HTTP

Endpoint

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

Authentication

Pulumi access token with organization RBAC, via browser authorization or bearer token.

Requirements

• Pulumi account; Pulumi Cloud organization for Cloud tools
• A separate Pulumi MCP access token for hosted use; use least-privilege organization token where possible
• Pulumi CLI for the local package route
• Resource search and Pulumi Neo require eligible paid editions; Neo usage is billed

Setup steps

1. Recommended hosted: add https://mcp.ai.pulumi.com/mcp using client remote Streamable HTTP setup. Authenticate in the browser with a dedicated Pulumi token, select organization, authorize, return to client.
2. Claude Code: claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcp; then /mcp and authenticate.
3. Cursor: add remote URL to .cursor/mcp.json, then Connect in Settings > Tools & MCP.
4. Claude Desktop: Settings > Connectors > Add custom connector; enter the hosted URL; restart and authenticate.
5. For headless clients, configure Authorization: Bearer ${PULUMI_MCP_TOKEN} and optional X-Pulumi-Org; use secret/environment storage.
6. Local legacy package is a separate option: follow current official package instructions and authenticate Pulumi CLI; do not confuse it with the hosted endpoint.
7. Verify by listing stacks or querying a harmless Registry schema. Deny neo-bridge in client permissions if you require read-only behavior.

Current Pulumi reference lists 14 tools for the hosted server and 11 for the local server; the stored 14 names correspond to the hosted OAuth service and include the `deploy-to-aws` prompt only if actually exposed as a prompt, so check actual tool row count: here all 14 are the hosted tool inventory already represented in this record. Local names are a different 11-tool set and are not merged.

• get-stacks

  List the stacks in the Pulumi organization.

  01
• resource-search

  Search resources across Pulumi stacks.

  02
• get-policy-violations

  List policy-as-code violations for stacks.

  03
• get-users

  List organization members and roles.

  04
• neo-bridge

  Start a Neo task, send follow-up messages, and approve or reject requests.

  05
• neo-get-tasks

  List organization Neo tasks and statuses.

  06
• neo-continue-task

  Read current status and events for a Neo task.

  07
• neo-reset-conversation

  Clear tracked state for a Neo 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 a resource’s properties and documentation.

  11
• get-function

  Get a function’s inputs, outputs, and documentation.

  12
• get-type

  Get the JSON schema for a type reference.

  13
• deploy-to-aws

  Return agent instructions for analyzing and generating Pulumi code to deploy an app to AWS.

  14

• `neo-bridge` can incur paid Neo usage and can lead to infrastructure changes or pull requests after approval; other registry tools and most cloud tools are read-only. Availability for some features depends on Pulumi edition.

• The legacy @pulumi/mcp-server local package and current hosted service are separate deployment paths and may expose different tool catalogs. The current docs? hosted catalog was used for hosted capability claims.

• official tool reference

  Current Pulumi tool reference enumerates hosted and local MCP tool surfaces and the deploy-to-aws prompt.

• official setup guide

  Current setup guide documents hosted endpoint, OAuth and local package/CLI requirements.

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