---
title: "Pulumi hosted MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/pulumi-hosted/
description: "Inspect Pulumi stacks, resources, policies and registry schemas, with optional delegation to Pulumi Neo."
---

# Pulumi hosted MCP: review, setup & limitations · Undominated.ai

> Inspect Pulumi stacks, resources, policies and registry schemas, with optional delegation to Pulumi Neo.

[← Explore all mcp servers](/mcp-servers/)

INFRASTRUCTURE DEVELOPMENT / Pulumi

# Pulumi hosted MCP

Inspect Pulumi stacks, resources, policies and registry schemas, with optional delegation to Pulumi Neo.

 [See setup guidance ↓](#setup)[Original source ↗](https://www.pulumi.com/docs/ai/mcp-server/)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 1 linked sources
 Publisher Pulumi
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Pulumi Model Context Protocol server”

 [Pulumi · upstream description ↗](https://www.pulumi.com/docs/ai/mcp-server/) Our analysis follows below.

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.

### A good fit for

 - Finding which stacks contain a resource before preparing an infrastructure change.
- Comparing a policy violation with a provider schema, while keeping Neo task creation disabled for inspection-only work.
- Inspecting Pulumi Cloud state from an agent that can reach a remote streamable-HTTP server and present a Pulumi token
- Not as a read-only agent unless Neo is also denied in the agent’s tool permissions

### Weigh up before choosing

 - Deny neo-bridge in the MCP client for a read-only workflow. A read-only organisation token alone is not the documented control for Neo tasks.
- A missing or inaccessible X-Pulumi-Org value can silently select the first accessible organisation. Check the returned organisation before acting.
- This is the hosted service. Its implementation licence and revision were not established; the older local package is not bundled.
- The page says restricting the token’s role is not enough on its own to prevent Neo tasks.
- Agents that only support stdio are told to use a proxy rather than the remote URL alone.
- No licence was stated on this page, and none was inferred.
- This review did not execute the resource.
- The server was not called.
- Do not reuse CLI credentials by assumption; reconnect to change the default organization or supply an organization explicitly to an applicable tool.

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.

[Upstream setup instructions ↗](https://www.pulumi.com/docs/ai/mcp-server/)

DOCUMENTED COMMAND

 claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcp Copy command ↗

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"
 }
 }
} Copy configuration ↗

### Compatibility

Claude Code · Claude Desktop · Cursor · Windsurf · Streamable HTTP clients with OAuth

### Transports

Streamable HTTP

### Hosted service

 - Account reads use the supplied token identity and organisation RBAC.
- neo-bridge can start tasks, send messages and approve Neo actions that may change infrastructure or open pull requests.

### Cost model

Registry and inventory reads have the documented account/edition requirements. Neo tasks and approvals incur Neo usage; no monetary rate was reviewed.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pulumi hosted MCP: clients, authentication, tool permissions and costs ↗](https://www.pulumi.com/docs/ai/mcp-server/) Checked 2026-10-14 https://www.pulumi.com/docs/ai/mcp-server/ Supports: install, configExample, access, limitations, bestFor, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Terraform MCP Server ↗ Looks up Terraform Registry documentation and can manage HCP Terraform or Terraform Enterprise workspaces and runs.](/mcp-servers/terraform/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
