CircleCI
by CircleCI
Diagnose failed builds, read job logs, inspect test results and rerun or roll back deployments from your AI assistant. 24 tools, OAuth2 or API token, hosted by CircleCI.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect CircleCI via MCP
https://mcp.circleci.com/v1/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect CircleCI once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioCircleCI Tools & Capabilities (24)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The hosted server is in preview. CircleCI states plainly that you can expect changes to the available tools during this phase, and points users at its community forum for feedback. Do not build anything load-bearing on a specific tool name.
- Rollbacks require prior setup. Deploy markers must be configured, the code must live in a GitHub repository, and the CircleCI GitHub App must be installed in the organisation. Without those,
rollback_deploy_componenthas nothing to act on. download_usage_datacaps at a 31-day range per call, per CircleCI's tool reference. Longer reporting periods need multiple calls.- API rate limits apply, and they are not generous for polling. CircleCI's API v2 index states a limit of 5,000 requests per hour per token, and its developer guide warns that the API protects against sudden bursts and sustained high volumes such as frequent polling. Throttled requests return HTTP 429, usually with a
Retry-Afterheader. The MCP endpoint itself returnedratelimit-limit: 50per second in our probe on 2026-09-08. - No config authoring, orb publishing, context or environment-variable management. CircleCI assigns all of that to the CLI MCP, not the hosted server. If you need it, connect the CLI MCP as well.
- Read-only tools cannot fix anything. The server surfaces logs, tests and artifacts; applying a fix still means editing your repository. The only writes available are rerun, cancel and rollback.
- We could not read the server's tool annotations. The endpoint requires authentication, so the read/write classification on this page rests on CircleCI's documentation rather than on MCP safety annotations from the server.
- Tool counts disagree between sources. Anthropic's directory lists 24 tools where CircleCI's documentation table lists 13, with several names differing. See the comparison above.
Frequently asked questions
No. CircleCI's connection guide lists only a CircleCI account with access to the projects you want to inspect, plus an MCP host that supports remote servers over streamable HTTP. Rollback tooling is the exception: CircleCI's rollback setup guide requires a GitHub repository, the CircleCI GitHub App, and configured deploy markers before any rollback can run.
Both, and OAuth2 is the recommended path. CircleCI's docs say most MCP hosts detect the OAuth2 requirement and prompt you to sign in on first connect. A personal API token sent as a bearer header is the documented fallback, intended only for hosts that cannot complete an OAuth2 flow, or for headless use.
Yes. Four of the 24 tools change CI/CD state: cancel_workflow, rerun_workflow, rollback_deploy_component and validate_config, of which the first three act on live infrastructure. CircleCI's own best-practice guidance says to review destructive actions before confirming them, noting this matters most on a shared or production-facing project.
Restart your MCP host or reconnect the server. CircleCI's troubleshooting section states that after it releases new tools, an MCP host must be restarted or the server reconnected before the updated list loads. The hosted server is in preview, so CircleCI warns that the available tools will change during this phase.
The hosted server runs at mcp.circleci.com and exposes a curated set of tools for observing and acting on CI runs. The CLI MCP runs locally and exposes the entire CircleCI CLI, including config authoring, orb tooling, policy and runner management. CircleCI recommends the hosted server for day-to-day diagnostic work.
Only if you choose the token fallback, and CircleCI advises against storing it in plain config. Its token guide notes that manually created personal API tokens grant full read and write permissions, while tokens issued through the OAuth flow are scoped to the Read, Write or Admin level the user picks at authorization time.
Sources
- CircleCI MCP overview (fetched 2026-09-08, page last updated 2026-09-01; read as Markdown via
/index.md). Supplied the hosted-vs-CLI split, the 13-tool table, best practices, example workflows and troubleshooting. · retrieved 2026-09-08 - Connecting to the CircleCI MCP server (fetched 2026-09-08). Supplied prerequisites, the OAuth2 and token paths, and client setup. · retrieved 2026-09-08
- Managing API tokens (fetched 2026-09-08). Supplied personal-token permissions and expiry. · retrieved 2026-09-08
- OAuth 2.0 API access with Dynamic Client Registration (fetched 2026-09-08). Supplied PKCE, user-selected scopes and the 90-day token lifetime. · retrieved 2026-09-08
- Rollback a deployment (fetched 2026-09-08). Supplied rollback behaviour and the current-version concurrency guard. · retrieved 2026-09-08
- Set up a rollback pipeline (fetched 2026-09-08). Supplied the rollback prerequisites. · retrieved 2026-09-08
- Deployment and deploy management overview (fetched 2026-09-08). Supplied the deploy-marker model. · retrieved 2026-09-08
- CircleCI API developer's guide — and API v2 index (both fetched 2026-09-08). Supplied the 5,000-per-hour limit and the 429 /
Retry-Afterbehaviour. · retrieved 2026-09-08 - Anthropic Connectors Directory entry (snapshot 2026-09-08). Supplied the 24 tool names,
partnertier, endpoint and transport. · retrieved 2026-09-08 - Authentication check against
https://mcp.circleci.com/v1/mcp— 2026-09-08. An anonymous connection attempt returned HTTP 401 with aWWW-Authenticate: Bearerchallenge, and the server's own RFC 9728 descriptor at/.well-known/oauth-protected-resourcenameshttps://app.circleci.comas its authorization server. No tool was called and no credential was supplied. · retrieved 2026-09-08
Server Info
- Category
- Developer Tools
- Developer
- CircleCI
- Tools
- 24
- Domain
- mcp.circleci.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Developer Tools
Related Resources
Ready to connect CircleCI?
Connect CircleCI once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.