← back to the directory
MCP Server Automation & IntegrationCoding

CircleCI MCP

1Official 2CircleCI 3pipeline 4and 5failure 6server

the six Ws · specification

W1 Who

Developers on CircleCI who want an agent to investigate failing pipelines and flaky tests.

W2 What

CircleCI's official MCP server surfaces pipeline, workflow, job, and test-insight data, including failed-test log retrieval, to MCP clients.

W3 Where

Runs locally via npx or Docker and calls the hosted CircleCI Cloud or server API.

W4 When

Invoked right after a CI failure so an agent can pull logs and suggest a fix in the same session.

W5 Why

Closes the loop between a red build and a code fix without the developer leaving the editor.

W6 With

Requires a CircleCI personal API token and project or org scoping to fetch pipeline data.

W7 Watch

Official, maintained under the CircleCI-Public GitHub organization, open source under the MIT license; read-mostly access to build data with the token carrying whatever project permissions it was issued.

ci-cdpipelinestest-failuresdevopsofficial

for agents & scripts

Reading this as a machine? Query it directly.

Search is open JSON - no key. Report telemetry after using a tool and it feeds that tool’s Proof Score. Or speak MCP to /mcp and discover tools mid-loop.