Pulumi MCP Server

Connect AI assistants to Pulumi Cloud, stacks, resources, the Pulumi Registry, and Pulumi Neo through MCP.

Cloud Platforms
No ratings
UpdatedNov 11, 2026

Install Pulumi MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)

Server URL

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

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpoint

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint

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

Overview

Infrastructure as code

Pulumi MCP Server connects AI assistants with Pulumi Cloud and Pulumi infrastructure as code through the Model Context Protocol. It exposes access to stacks, resources, the Pulumi Registry, and Pulumi Neo, with authentication handled by browser sign-in or a Pulumi access token. Reach for it when an AI assistant needs Pulumi project context or infrastructure information.

Use cases

Inspect Pulumi stacks and resources from an AI assistant
Look up packages and providers in the Pulumi Registry
Use Pulumi Cloud context in infrastructure discussions
Connect headless AI workflows with a Pulumi access token

Key features

Hosted MCP connection for Pulumi Cloud
Access to Pulumi stacks and resources
Pulumi Registry access
Pulumi Neo access
Browser-based authentication
Bearer-token authentication for headless use

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

How Pulumi MCP Server works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pulumi MCP Server

Pulumi MCP Server is an MCP server that connects AI assistants to Pulumi Cloud and Pulumi infrastructure as code. Its main tools provide access to stacks, deployed resources, the Pulumi Registry, and Pulumi Neo. Authentication uses a Pulumi access token, either through browser sign-in or as a bearer token for headless operation.

Authenticate through Pulumi’s browser sign-in flow for interactive use, or provide a Pulumi access token as a bearer token for headless operation.

It can access Pulumi Cloud, Pulumi stacks, Pulumi resources, the Pulumi Registry, and Pulumi Neo through MCP.

Yes, headless use is supported with a Pulumi access token passed as a bearer token instead of browser-based sign-in.

Related MCP servers

All in Cloud Platforms All alternatives

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Pulumi MCP Server AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/pulumi-remote-mcp?style=directory)](https://allmcps.com/mcp/pulumi-remote-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/pulumi-remote-mcp"><img src="https://allmcps.com/api/badge/pulumi-remote-mcp?style=directory" alt="Pulumi MCP Server on AllMCPs" /></a>