Pulumi MCP Server for Cline 11 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Pulumi through the Vinkius and Cline gains direct access to every tool — from data retrieval to workflow automation — without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Pulumi and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"pulumi": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About Pulumi MCP Server
Connect your Pulumi account to any AI agent and take full control of your infrastructure-as-code through natural conversation.
Cline operates autonomously inside VS Code — it reads your codebase, plans a strategy, and executes multi-step tasks including Pulumi tool calls without waiting for prompts between steps. Connect 11 tools through the Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
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)
The Pulumi MCP Server exposes 11 tools through the Vinkius. Connect it to Cline in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Pulumi to Cline via MCP
Follow these steps to integrate the Pulumi MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Pulumi
Ask Cline: "Using Pulumi, help me..." — 11 tools available
Why Use Cline with the Pulumi MCP Server
Cline provides unique advantages when paired with Pulumi through the Model Context Protocol.
Cline operates autonomously — it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Pulumi + Cline Use Cases
Practical scenarios where Cline combined with the Pulumi MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Pulumi and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Pulumi tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Pulumi and generates snapshot tests or mocks based on actual payloads
Incident response: query Pulumi for real-time status and let Cline generate hotfix patches based on the findings
Pulumi MCP Tools for Cline (11)
These 11 tools become available when you connect Pulumi to Cline via MCP:
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
Example Prompts for Pulumi in Cline
Ready-to-use prompts you can give your Cline agent to start working with Pulumi immediately.
"Show me all stacks in my organization."
"What was the result of the latest deployment to my-infra/prod?"
"Show me the exported outputs from the prod stack."
Troubleshooting Pulumi MCP Server with Cline
Common issues when connecting Pulumi to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Pulumi + Cline FAQ
Common questions about integrating Pulumi MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Pulumi with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Pulumi to Cline
Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.