Control CircleCI from Your IDE with Natural Language

Stop switching between your IDE and CircleCI's web interface. This MCP server puts CircleCI's entire workflow at your fingertips through natural language commands, directly in Cursor, VS Code, Claude Desktop, or Windsurf.

Debug Builds Without Context Switching

You know the drill: pipeline fails, you tab over to CircleCI, navigate to the failed job, scroll through logs, copy error messages back to your IDE. This server eliminates that workflow entirely.

Instead of hunting through the CircleCI interface:

"Find the latest failed pipeline on my main branch and get the logs"

You get formatted failure logs with job names, step details, and error context - all without leaving your editor. No more juggling browser tabs when you're deep in a debugging session.

Instant Pipeline Visibility

Check build status the same way you'd ask a teammate:

"What's the status of my latest pipeline?"
"Get test results for my current branch"
"Are there any flaky tests in this project?"

Each command returns structured information - workflow status, test results with failure details, flaky test detection with historical context. You get the data you need formatted for immediate action.

One-Command Pipeline Operations

Trigger builds and rerun failed workflows without switching contexts:

"Run the pipeline for this branch"
"Rerun the failed workflow from where it broke"

The server handles project detection from your local git context, so it knows which CircleCI project to target based on your current working directory.

Real-World Workflow Integration

This shines in common debugging scenarios:

Morning standup prep: "List my CircleCI projects and check the latest pipeline status for each" - get a full picture of your builds without opening CircleCI.

Failed build investigation: "Get build failure logs for the main branch" → analyze the error → "Get test results to see which specific tests failed" → fix the issue → "Run the pipeline again."

Test suite maintenance: "Find flaky tests in my project" gives you CircleCI's flaky test detection data directly in your IDE, with detailed failure contexts for each problematic test.

Multiple Integration Options

Works with your existing setup:

• NPX: Single command installation, no additional dependencies
• Docker: Containerized deployment for team consistency
• IDE Support: Native integration with Cursor, VS Code, Claude Desktop, Windsurf, and Claude Code

Quick Setup

Add this to your IDE's MCP configuration:

{
  "mcpServers": {
    "circleci-mcp-server": {
      "command": "npx",
      "args": ["-y", "@circleci/mcp-server-circleci"],
      "env": {
        "CIRCLECI_TOKEN": "your-circleci-token"
      }
    }
  }
}

Smart Context Detection

The server intelligently determines your CircleCI project through multiple methods:

1. Local git context - automatically detects your project from the current repository
2. CircleCI URLs - paste any CircleCI URL and it extracts the relevant project info
3. Project selection - list your followed projects and choose the one you want to work with

This means you spend zero mental overhead on configuration - just ask for what you need and it figures out the context.

The CircleCI MCP server transforms CircleCI from a separate tool you have to visit into a natural extension of your development environment. Instead of breaking flow to check build status or debug failures, you get the information and control you need through the same interface where you're already working.