| name | pulumi-mcp-connector |
| description | MCP connector for Pulumi infrastructure as code – enables AI-powered infrastructure definition, stack management, and cloud resource provisioning through Claude |
| license | Apache 2.0 |
| tags | ["cloud","iac","mcp","pulumi","infrastructure"] |
| difficulty | advanced |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Pulumi MCP Connector
Overview
This skill enables Claude to interact with Pulumi through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Pulumi's CLI/Automation API, allowing natural language control of Pulumi operations, intelligent automation, and AI-powered assistance for Pulumi workflows.
When to Use This Skill
- Infrastructure code generation in multiple languages
- Stack configuration and secret management
- Resource dependency graph analysis
- Drift detection and remediation
- Multi-cloud resource provisioning
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Pulumi │
│ (Client) │◀────│ (TypeScript) │◀────│ (CLI/Automation)│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Pulumi operations as tools Claude can invoke. The server translates natural language intentions into CLI/Automation API calls.
Key Endpoints/Interfaces
pulumi up, pulumi preview, pulumi stack, pulumi config, pulumi import
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "pulumi-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Pulumi resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}pulumi up`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"pulumi-mcp-connector": {
"command": "node",
"args": ["path/to/pulumi-mcp-connector/index.js"],
"env": {
"PULUMI_API_KEY": "your-api-key",
"PULUMI_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Pulumi API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Pulumi API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Generate Pulumi TypeScript code for a VPC with public/private subnets, NAT gateway, and an EKS cluster"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
