How to Use the CircleCI MCP in Cursor

Q: How do I trigger a CircleCI pipeline from the Cursor sidebar?

Ask the Cursor agent to kick off a run. It uses triggerccipipeline to launch the build and keeps you updated in the chat.

Q: Can Cursor show me why a CircleCI job failed?

Yes. The agent calls getjobdetails to read the build log, diagnoses the failure, and offers to fix the bug in your code.

Q: How do I configure this CircleCI MCP Server for my Cursor project?

Add the server details to your local .cursor/mcp.json file. Once saved, the editor agent instantly gains access to all eight build tools.

Q: Can I list workflow contexts directly inside the editor?

Yes, the agent runs listccicontexts to show you your organization's shared variables without making you leave your workspace.

Let your Cursor agent trigger, track, and debug CircleCI builds while writing code in your editor.

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 Cursor

Create your Vinkius account to connect CircleCI to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug broken builds in Cursor Agent mode

`get_job_details` pulls the exact failure logs from your broken build directly into your active Cursor editing session. The agent reads the compiler error and fixes the local code in one step. By calling `list_workflow_jobs` through this MCP link, the editor agent maps out the entire failing pipeline. You don't have to copy-paste terminal errors because the tool feeds the raw build context straight to the LLM.

Trigger pipelines inside this Cursor MCP Server

`trigger_cci_pipeline` starts a fresh build directly from the Cursor chat sidebar. You write a feature, commit it, and tell the agent to test it without leaving your keyboard. The agent verifies your active credentials with `get_my_cci_profile` before launching the run. This keeps your build cycles tight and your hands on the home row.

Audit your workflow contexts while writing code

`list_cci_contexts` displays your organization's shared variables directly inside the Cursor editor. You can verify if a secret exists before writing the code that depends on it. To track how these contexts affect your runs, `list_cci_pipelines` fetches the history of your active branches. You get the full picture of your build environment right next to your open files.

Setup guide

Set up CircleCI MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the CircleCI MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent CircleCI transactions." If the MCP tools are loaded correctly, Cursor will call the CircleCI tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Ask the Cursor agent to kick off a run. It uses `trigger_cci_pipeline` to launch the build and keeps you updated in the chat.

Yes. The agent calls `get_job_details` to read the build log, diagnoses the failure, and offers to fix the bug in your code.

Add the server details to your local `.cursor/mcp.json` file. Once saved, the editor agent instantly gains access to all eight build tools.

Yes, the agent runs `list_cci_contexts` to show you your organization's shared variables without making you leave your workspace.

Your credentials reside locally in your configuration file or securely in your Vinkius environment. The MCP server processes your build logs and context names in memory without persistent external logging.

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