Creativity · MCP — server

MCP CircleCI Server

CircleCI is a widely used cloud CI/CD platform. The MCP CircleCI Server wraps its v2 API to expose pipelines, workflows, and jobs as MCP tools — letting Claude investigate why a build failed, fetch logs, and (optionally) rerun a broken job.

MCP facts

Kind: server
Ecosystem: anthropic-mcp
Language: TypeScript / Node.js
Transports: stdio

Capabilities

Tools: list_projects, list_pipelines, get_workflow, get_job, get_job_logs, rerun_workflow
CircleCI v2 API auth via personal token
Supports self-hosted runner-based projects

Install

npx -y @modelcontextprotocol-community/server-circleci

Configuration

{
  "mcpServers": {
    "circleci": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol-community/server-circleci"],
      "env": {
        "CIRCLECI_TOKEN": "<personal-token>"
      }
    }
  }
}

Frequently asked questions

Can the model start a new pipeline?

Yes — trigger_pipeline is available and useful for re-running flaky jobs. Guard it with MCP client approval for production pipelines.

How do job logs come back?

Chunked and truncated to fit a reasonable token window. For deep log inspection, have Claude ask for specific step output only.

Does it work with orbs?

Yes — the API surface for orbs is exposed so the model can look up publicly available orbs and suggest config snippets.

Sources

CircleCI API v2 — accessed 2026-04-20
Model Context Protocol — accessed 2026-04-20