INFRASTRUCTURE DEVELOPMENT / Pulumi
Pulumi hosted MCP
Inspect Pulumi stacks, resources, policies and registry schemas, with optional delegation to Pulumi Neo.
“Pulumi Model Context Protocol server”
01 / THE REASONING
Why this made the selection.
- Combines account-specific infrastructure inventory with public resource schemas.
- Documents the distinct Neo delegation permission and billing boundary instead of describing every tool as read-only.
- Pulumi hosts the MCP server at https://mcp.ai.pulumi.com/mcp and says there is nothing to install locally.
- Calls use a Pulumi access token, and the page says restricting that token’s role is not enough by itself to stop Neo tasks.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Pulumi hosted MCP: clients, authentication, tool permissions and costs
- https://www.pulumi.com/docs/ai/mcp-server/
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The current official guide documents a hosted endpoint, browser and bearer authentication, and a separate Neo delegation boundary.
- The public pulumi/mcp-server repository returned 404 during review, so no local source licence or pinned implementation is claimed.
- Pulumi documents a hosted server at https://mcp.ai.pulumi.com/mcp with nothing to install or run locally. Remote clients use streamable HTTP with OAuth.
- The server calls Pulumi Cloud with a token the user provides, and the agent can see and do what that token can under the organization’s RBAC, and nothing more.
- The page says restricting the token’s role is not enough on its own to prevent Neo tasks; the agent also has to deny the Neo bridge if the agent should stay read-only.
- The hosted browser flow stores a separate Pulumi access token and default organization; a read-only token role alone is not the documented control for Neo tasks.
Not established by this review
- Installation, authentication and live tool execution were not tested.
- Service availability, security isolation and package/container parity with source were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcp Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Add the hosted URL using the client-specific configuration; the shown JSON uses Cursor’s mcpServers wrapper.
- Authenticate in the browser with a dedicated Pulumi access token and choose the intended organisation. Use an organisation-scoped token where your plan and task permit.
- For headless access, use an Authorization bearer header and X-Pulumi-Org from the documented example. Verify how the client expands secret variables.
- Inspect the tool list and deny neo-bridge when task creation, approvals or infrastructure changes are outside scope.
- Create a dedicated MCP token, select the intended default organization and also deny neo-bridge in the agent when read-only use is required.
Before you start
- A client supporting remote Streamable HTTP and the documented authentication flow.
- A Pulumi account and dedicated access token; some tools require additional Pulumi Cloud editions.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"pulumi": {
"url": "https://mcp.ai.pulumi.com/mcp"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://www.pulumi.com/docs/ai/mcp-server/
Supports: install, configExample, access, limitations, bestFor, review