MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Pulumi MCP Server

Name: Pulumi
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR ToolsFree for Subscribers

Manage cloud infrastructure via Pulumi — list stacks, track deployments, audit outputs and tag resources from any AI agent.

Get MCP Server for AI Agents

Ask AI about this MCP Server

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

What is the Pulumi MCP Server?

The Pulumi MCP Server gives AI agents like Claude, ChatGPT, and Cursor direct access to Pulumi via 11 tools. Manage cloud infrastructure via Pulumi — list stacks, track deployments, audit outputs and tag resources from any AI agent. Powered by the Vinkius - no API keys, no infrastructure, connect in under 2 minutes.

Built-in capabilities (11)

create_stackdelete_stackget_current_userget_deploymentget_organizationget_stackget_stack_outputslist_deploymentslist_stack_tagslist_stacksset_stack_tag

Tools for your AI Agents to operate Pulumi

Ask your AI agent "Show me all stacks in my organization." and get the answer without opening a single dashboard. With 11 tools connected to real Pulumi data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.

Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by the Vinkius - your credentials never touch the AI model, every request is auditable. Connect in under two minutes.

Why teams choose Vinkius

One subscription gives you access to thousands of MCP servers - and you can deploy your own to the Vinkius Edge. Your AI agents only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure and security, zero maintenance.

Build your own MCP Server with our secure development framework →

Vinkius works with every AI agent you already use

…and any MCP-compatible client

Pulumi MCP Server capabilities

11 tools

create_stack

A stack is an isolated, independently configurable instance of your Pulumi program. Requires the org name, project name and stack name (e.g. "staging", "prod"). Returns the created stack with its URL. Create a new Pulumi stack

delete_stack

The stack must be empty (no resources) or force deletion must be enabled. Provide the org name, project name and stack name. WARNING: this action is irreversible. Delete a Pulumi stack

get_current_user

Returns the user's GitHub login, avatar URL, email and name. Use this to verify your access token is working correctly and to see which identity the API calls will appear as. Get the currently authenticated Pulumi user

get_deployment

Provide the org name, project name, stack name and deployment version number. Get details for a specific Pulumi deployment

get_organization

Provide the organization name (slug). Get details for a specific Pulumi organization

get_stack

Provide the org name, project name and stack name. Get details for a specific Pulumi stack

get_stack_outputs

Outputs are values your Pulumi program exports, such as URLs, IP addresses, resource IDs and connection strings. Useful for discovering endpoint addresses and configuration values after infrastructure deployment. Get the exported output values from a Pulumi stack

list_deployments

Each deployment shows its version number, status (succeeded, failed, in-progress), start/end time, resource changes (created, updated, deleted) and the user who triggered it. Use this to audit infrastructure changes and track deployment success/failure patterns. List deployment history for a Pulumi stack

list_stack_tags

Tags are key-value metadata labels used for organizing, filtering and managing stacks (e.g. environment=prod, team=platform, cost-center=engineering). List tags on a Pulumi stack

list_stacks

Each stack represents an isolated, independently configurable instance of your infrastructure (e.g. dev, staging, prod). Returns stack name, project name, last update info, resource count and whether updates are in progress. List all stacks in a Pulumi organization

set_stack_tag

Tags are used for organizing, filtering and managing stacks (e.g. key="environment", value="prod", key="team", value="platform"). Provide the org name, project name, stack name, tag name and tag value. Set a tag on a Pulumi stack

What the Pulumi MCP Server unlocks

Connect your Pulumi account to any AI agent and take full control of your infrastructure-as-code through natural conversation.

What you can do

Organization Discovery — List organizations and retrieve their details, team settings and member info
Stack Management — List, create and delete stacks (infrastructure environments) across all your projects
Deployment Tracking — Monitor stack update history with status (succeeded, failed, in-progress), resource changes and error logs
Output Inspection — View exported output values from the latest deployment (URLs, IPs, resource IDs)
Tag Management — List and set custom tags on stacks for organization and filtering (environment, team, cost-center)

How it works

1. Subscribe to this server
2. Enter your Pulumi Access Token
3. Start managing your infrastructure from Claude, Cursor, or any MCP-compatible client

No more switching to the Pulumi Console to check deployment status or review stack outputs. Your AI acts as a dedicated infrastructure operations engineer.

Who is this for?

DevOps Engineers — quickly check stack status, review deployment history and inspect outputs without opening the Pulumi Console
Platform Teams — audit infrastructure changes, track deployment success rates and manage stack tags across organizations
Developers — discover available stacks, review exported endpoints and verify resource provisioning via conversation

Frequently asked questions about the Pulumi MCP Server

How do I get a Pulumi Access Token?

Log in to the Pulumi Console, go to Account Settings > Access Tokens, click Create Token, give it a name and copy the token immediately — it starts with pul_ and won't be shown again.

What is a Pulumi stack?

A stack is an isolated, independently configurable instance of your Pulumi program. Stacks typically represent different environments like dev, staging and prod. Each stack has its own configuration, state, outputs and deployment history. Use list_stacks to discover all stacks in an organization.

Can I see the deployment history of a stack?

Yes! Use list_deployments with the org name, project name and stack name. It returns the update history showing version number, status (succeeded, failed, in-progress), start/end time and resource change counts. Use get_deployment with a specific version for detailed logs and error messages.

Can I view the outputs of a stack?

Yes! Use get_stack_outputs with the org name, project name and stack name. It returns all exported output values from the latest successful deployment, such as URLs, IP addresses, resource IDs and connection strings. This is useful for discovering endpoint addresses after infrastructure deployment.