# Pulumi MCP Server [Official] [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://www.pulumi.com/docs/iac/guides/ai-integration/mcp-server/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/pulumi-remote-mcp

## Description
Pulumi's official hosted MCP server. Gives AI assistants access to Pulumi Cloud and infrastructure as code: stacks, resources, the Pulumi Registry and Neo. Sign in with a Pulumi access token in the browser, or pass it as a bearer token for headless use.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://www.pulumi.com/docs/iac/guides/ai-integration/mcp-server/), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

```sh
claude mcp add --transport http pulumi https://mcp.ai.pulumi.com/mcp
```

## Documentation

## What Pulumi MCP Server does

Pulumi MCP Server gives AI assistants an MCP connection to Pulumi Cloud and Pulumi infrastructure as code. Through that connection, assistants can work with Pulumi concepts including stacks and resources, consult the Pulumi Registry, and access Pulumi Neo.

The server is intended for workflows where an AI assistant needs information from a Pulumi environment or needs to use Pulumi’s infrastructure-as-code context while responding to a developer. Its scope centers on Pulumi Cloud and related Pulumi services rather than general cloud-provider access.

## How it works

The server exposes Pulumi capabilities through MCP so that a compatible AI assistant can request information using the tools made available by the server. Pulumi Cloud supplies the connected infrastructure context, while the Pulumi Registry and Pulumi Neo are additional Pulumi surfaces available through the integration.

Authentication can happen interactively in a browser. For unattended or headless workflows, the client can send a Pulumi access token as a bearer token when connecting to the hosted server.

## Setup and configuration

Use the hosted Pulumi MCP Server as the MCP endpoint for an AI assistant that supports MCP connections. Interactive use can authenticate through Pulumi’s browser sign-in flow.

Headless operation uses a Pulumi access token passed as a bearer token. This approach is suitable for environments where browser-based sign-in is unavailable, such as automated or remote workflows. Keep the token in the client or runtime’s secure configuration rather than exposing it in prompts or source code.

The connection requires an MCP-compatible AI assistant and valid Pulumi authentication. The available Pulumi context depends on the account and access represented by the token or browser session.

## Tools and capabilities

Pulumi MCP Server provides access to these Pulumi areas:

- Pulumi Cloud
- Pulumi stacks
- Pulumi resources
- The Pulumi Registry
- Pulumi Neo

These capabilities let an assistant use Pulumi environment and infrastructure context while working through MCP. The server is especially relevant for questions or tasks involving existing Pulumi stacks, their resources, registered Pulumi packages or providers, and Pulumi Neo.

## Limitations and notes

Access is governed by Pulumi authentication. Browser sign-in is available for interactive use, while headless clients must provide a Pulumi access token as a bearer token. The server’s scope is tied to Pulumi Cloud and Pulumi’s infrastructure-as-code ecosystem; it should be evaluated based on whether those are the systems an assistant needs to access.

_Full upstream README: https://allmcps.com/mcp/pulumi-remote-mcp/readme_