CircleCI MCP Server

CircleCI's own hosted MCP server connects your agent to your CircleCI runs, so you can diagnose build failures, read logs and act on workflows without leaving the chat. What you can do with it - List recent runs for a project, or your own runs across projects, filtered by branch or status - Drill into a run's workflows, jobs and steps, with each step's exit code and any config errors - Read a job's logs; when you don't name a step, it reads the failed ones - See which tests failed in a job, and list the files it saved, such as test reports, coverage or build output - Rerun a workflow from the start or only from its failed jobs, or cancel one that's running - Export an organization's usage data as CSV files, up to 31 days at a time How it connects CircleCI hosts it at https://mcp.circleci.com/v1/mcp, and it's listed in Claude's connector directory and Cursor's MCP marketplace. Most agents ask you to sign in to CircleCI with OAuth the first time you connect. If yours can't, or for headless use, send a CircleCI personal API token as a bearer token in the Authorization header. CircleCI's guides cover Claude, Claude Code, Cursor, VS Code and Windsurf. Good to know - Rerunning or canceling a workflow changes real CI state, so check what your agent is about to do, especially on shared projects. - For config authoring, orbs, contexts and other admin tasks, CircleCI points to the MCP server built into the CircleCI CLI instead. Its older npx-based local server is deprecated. - When CircleCI adds tools, reconnect the server to load them.