How to Use the CircleCI MCP in VS Code Copilot

Q: How does VS Code Copilot help me debug a failing CircleCI job?

Copilot calls getjobdetails to pull the build logs, analyzes the failure, and highlights the broken code line in your editor.

Q: How do I share this CircleCI MCP configuration with my engineering team?

Commit the server settings to your repo in .vscode/mcp.json. Every developer on your team will automatically get access to these build tools.

Q: Can I view pipeline workflows without leaving my workspace?

Yes, the MCP agent uses listpipelineworkflows to show you all active runs and their current execution status.

Connect VS Code Copilot to CircleCI to trigger pipelines and inspect failed jobs directly from your workspace.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect CircleCI MCP to VS Code Copilot

Create your Vinkius account to connect CircleCI 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 CircleCI with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fix broken pipelines inside VS Code Copilot

`get_job_details` exposes the specific error messages from your failed runs directly to Copilot Chat. Your team's agent reads the failure details and suggests the exact code change needed to fix it. The agent runs `list_workflow_jobs` over the active MCP channel to see which upstream job blocked the deployment. You get the context you need to debug the build without opening a browser.

Run builds using the CircleCI MCP Server

`trigger_cci_pipeline` lets you kick off a new build cycle right from the VS Code terminal or chat panel. You don't have to push empty commits just to force a rerun. The agent checks `get_my_cci_profile` to make sure you have the right permissions before firing off the run. This ensures your team maintains clean access control over deployments.

Track team workflows across your repositories

`list_cci_pipelines` displays your project's recent build history inside VS Code Copilot. You can monitor active main branch builds while working on feature branches. For complex setups, `list_pipeline_workflows` and `get_workflow_details` break down multi-stage deployments. You see exactly where a package is stuck in the release chain.

Setup guide

Set up CircleCI 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 CircleCI 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 CircleCI tools listed. Try asking: "List my recent CircleCI transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "circleci-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 CircleCI. 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 CircleCI 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 CircleCI MCP in VS Code Copilot

Yes. Ask the Copilot agent to start a build, and it will execute `trigger_cci_pipeline` to run your current branch.

Copilot calls `get_job_details` to pull the build logs, analyzes the failure, and highlights the broken code line in your editor.

Commit the server settings to your repo in `.vscode/mcp.json`. Every developer on your team will automatically get access to these build tools.

Yes, the MCP agent uses `list_pipeline_workflows` to show you all active runs and their current execution status.

This server handles your organization's context names and build metadata in an ephemeral, zero-trust sandbox. Your pipeline secrets and access tokens are never saved or exposed to external LLM providers.

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