CircleCI MCP server

Last verified: 2026-09

Inspect pipelines and jobs.

Community Developer tools Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code, VS Code

What it does

CircleCI's official MCP: pipeline status, job logs, flaky tests, artifacts, reruns. Needs CIRCLECI_TOKEN.

It sits in Developer tools: Split this category in two.

Good for

Get the latest pipeline status and the job's failure logs.
Find flaky tests from execution history.
List artifacts after a build without opening the UI.
Leave rerun_workflow and run_rollback_pipeline unused until you mean it.

Tools

get_latest_pipeline_status / get_build_failure_logs / get_job_test_results — Why a build failed.
find_flaky_tests / find_underused_resource_classes / download_usage_api_data — Cost and flake analysis.
list_followed_projects / list_artifacts / list_component_versions — Inventory.
run_pipeline / rerun_workflow / run_rollback_pipeline / config_helper — Trigger and validate. Treat as write.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "circleci": {
      "command": "npx",
      "args": [
        "-y",
        "circleci-mcp-server"
      ],
      "env": {
        "CIRCLECI_TOKEN": "..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y circleci-mcp-server

Secrets it wants: CIRCLECI_TOKEN

Source repo →

How to get started

Create a CircleCI PAT with the smallest scope that can read the project.
Ask for the latest pipeline status on one project before enabling rerun tools.
Do not let it rollback prod on the first day.

Access risk

rerun_workflow and run_rollback_pipeline change prod. Token theft is CI access.

When to skip it

Skip it if you only need git history (Git) or GitHub Actions (GitHub official).

Instead: GitHub official, Sentry, Datadog.

Developer toolsGitHub officialGitHub's own MCP server (Go), remote or local. OfficialSentryList and inspect Sentry issues. Cloud & infraDatadogMetrics, logs, and monitors.

Vs alternatives

Server	Official?	Needs a secret?	Best for
CircleCI	No	Yes	Inspect pipelines and jobs.
GitHub official	No	Yes	GitHub's own MCP server (Go), remote or local.
Sentry	Yes	Yes	List and inspect Sentry issues.
Datadog	No	Yes	Metrics, logs, and monitors.

More in Developer tools

OfficialEverythingReference server that exercises the whole MCP protocol. OfficialGitRead a local git repo: log, diff, status. OfficialGitHubRepos, issues, PRs, and file contents on GitHub. OfficialGitLabProjects, issues, and merge requests on GitLab.

All 18 in this category →

FAQ

Which token?

CIRCLECI_TOKEN with the smallest scope that can read the project.

Can it ship a rollback?

run_rollback_pipeline is in the tool list. That is production. Do not enable it on day one.

CircleCI or GitHub Actions?

If Actions is your CI, use GitHub official. This server is CircleCI's API.

Official CircleCI?

Yes — CircleCI-Public/mcp-server-circleci.