4,000+ servers built on MCP Fusion
Vinkius
VS Code CopilotIDE
Why use Pulumi MCP Server with VS Code Copilot?

Bring Infrastructure As Code
to VS Code Copilot

Create your Vinkius account to connect Pulumi to VS Code Copilot and start using all 11 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Create StackDelete StackGet Current UserGet DeploymentGet OrganizationGet StackGet Stack OutputsList DeploymentsList Stack TagsList StacksSet Stack Tag
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Pulumi

What is the Pulumi MCP Server?

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

Built-in capabilities (11)

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

Why VS Code Copilot?

GitHub Copilot Agent mode brings Pulumi data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Pulumi in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Pulumi with Vinkius?

The Pulumi connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 11 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full Pulumi details →
Pulumi
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Pulumi using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Pulumi and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Pulumi to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Pulumi for VS Code Copilot

Every request between VS Code Copilot and Pulumi is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

06

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

07

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

08

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

09

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →