How to Use the Cloudify MCP in VS Code Copilot

Q: How do I share this Cloudify setup with my team in VS Code Copilot?

Put your configuration in .vscode/mcp.json and commit it to Git. Everyone on your engineering team gets access to the Cloudify tools instantly when they open the workspace.

Q: Can VS Code Copilot execute Cloudify blueprints directly?

Yes, when you set the editor to Agent mode. The agent uses listblueprints and getdeployment to read your infrastructure topology and help you write or debug your deployment steps.

Q: What is the best way to debug stuck workflows?

Ask your agent to use the MCP tool to run listexecutions on your active deployment. It will return the exact state of the running workflow so you can see which node failed.

Run and debug Cloudify deployments directly inside VS Code Copilot without leaving your active workspace.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Cloudify MCP to VS Code Copilot

Create your Vinkius account to connect Cloudify to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Cloudify with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Audit Cloudify blueprints inside VS Code Copilot

The `list_blueprints` tool identifies active schemas directly inside your editor. You can then run `get_blueprint` to extract specific structural properties without switching back to the web console. This MCP Server lets your team inspect node relationships and configuration properties directly in the sidebar. Catching schema errors early saves hours of debugging time.

Track live deployments and execution states

Running `list_deployments` retrieves runtime schemas to show you exactly what is currently active. Your agent can then pull down the exact structural states with `get_deployment` to debug failing nodes. If a deployment stalls, ask the agent to run `list_executions` to pinpoint where the workflow got stuck. You get real-time status updates right next to your application code.

Map infrastructure nodes and plugins

Calling `list_nodes` identifies specific instances and routing rules in your active cluster. Combine this with `list_plugins` to verify what native capabilities are installed in your environment. This means your agent can write accurate deployment scripts because it actually knows the target environment constraints. It checks the live system rules before suggesting configuration changes.

Setup guide

Set up Cloudify MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Cloudify MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Cloudify tools listed. Try asking: "List my recent Cloudify transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "cloudify-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Cloudify. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Cloudify now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Cloudify MCP in VS Code Copilot

Put your configuration in `.vscode/mcp.json` and commit it to Git. Everyone on your engineering team gets access to the Cloudify tools instantly when they open the workspace.

Yes, when you set the editor to Agent mode. The agent uses `list_blueprints` and `get_deployment` to read your infrastructure topology and help you write or debug your deployment steps.

No, you only need the Vinkius endpoint token. This MCP server handles the connection to your Cloudify manager in the background, keeping your local editor lightweight.

Ask your agent to use the MCP tool to run `list_executions` on your active deployment. It will return the exact state of the running workflow so you can see which node failed.

Your infrastructure schemas and deployment states never persist on Vinkius. The MCP connection runs in a secure, ephemeral V8 sandbox that only passes execution topologies directly to your local VS Code Copilot session.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript