Can I trigger a build for a specific branch through the agent?

Yes! Use the `trigger_cci_pipeline` tool. You need to provide the project slug (e.g., `gh/org/repo`) and the branch name. The agent will instruct CircleCI to start the pipeline immediately.

How do I see why a specific job failed?

Use the `get_job_details` tool with the project slug and job number. Your agent will fetch the execution status and metadata, which often points to the cause of failure.

Where do I find my CircleCI API Token?

Log in to CircleCI, go to **User Settings -> Personal API Tokens**. You can generate and copy a new token from there.

CircleCI MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: CircleCI
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install CircleCI and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 CircleCI MCP Server

Connect your CircleCI account to any AI agent and take full control of your CI/CD pipelines and software delivery through natural conversation. Streamline how you monitor and trigger automated builds.

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

What you can do

Pipeline Oversight — List and retrieve details for recent CI/CD pipelines across your organizations natively
Trigger Management — Manually trigger new pipeline runs for specific projects and branches flawlessly
Workflow Intelligence — Access detailed information for workflows and their constituent jobs securely
Job Auditing — Retrieve detailed metadata and execution status for specific jobs flawlessly
Context Logistics — List shared environment contexts used for securing sensitive project data flawlessly
Developer Insights — Retrieve your own user profile and organization membership information directly within your workspace

The CircleCI MCP Server exposes 8 tools through the Vinkius. Connect it to VS Code Copilot 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 CircleCI to VS Code Copilot via MCP

Follow these steps to integrate the CircleCI MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using CircleCI

Ask Copilot: "Using CircleCI, help me..." — 8 tools available

Why Use VS Code Copilot with the CircleCI MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with CircleCI through the Model Context Protocol.

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

CircleCI + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the CircleCI MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

CircleCI MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect CircleCI to VS Code Copilot via MCP:

get_job_details

Get detailed information for a specific job

get_my_cci_profile

Retrieve information about the authenticated user

get_workflow_details

Get detailed information for a specific workflow

list_cci_contexts

List shared contexts for an organization

list_cci_pipelines

List recent CI/CD pipelines

list_pipeline_workflows

List all workflows within a specific pipeline

list_workflow_jobs

List all jobs within a specific workflow

trigger_cci_pipeline

Trigger a new pipeline for a project

Example Prompts for CircleCI in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with CircleCI immediately.

"List my last 5 pipelines in CircleCI."

"Trigger a new pipeline for project 'gh/acme/api' on the 'main' branch."

"Show me the status of all jobs in workflow ID 'wf-12345'."

Troubleshooting CircleCI MCP Server with VS Code Copilot

Common issues when connecting CircleCI to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

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

CircleCI + VS Code Copilot FAQ

Common questions about integrating CircleCI MCP Server with VS Code Copilot.

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.

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.

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.

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.