Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Diagnose failed builds, read job logs, inspect test results and rerun or roll back deployments from your AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The CircleCI MCP server connects your CI/CD pipelines to Claude, ChatGPT and any MCP-compatible agent. It exposes 24 tools for finding out why a build failed, reading job logs and test results, listing build artifacts, and rerunning, cancelling or rolling back work that has already shipped. CircleCI hosts it, so nothing installs locally.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
rollback_deploy_component has nothing to act on.download_usage_data caps at a 31-day range per call, per CircleCI's tool reference. Longer reporting periods need multiple calls.Retry-After header. The MCP endpoint itself returned ratelimit-limit: 50 per second in our probe on 2026-09-08.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.
/index.md). Supplied the hosted-vs-CLI split, the 13-tool table, best practices, example workflows and troubleshooting. · retrieved 2026-09-08Retry-After behaviour. · retrieved 2026-09-08partner tier, endpoint and transport. · retrieved 2026-09-08https://mcp.circleci.com/v1/mcp — 2026-09-08. An anonymous connection attempt returned HTTP 401 with a WWW-Authenticate: Bearer challenge, and the server's own RFC 9728 descriptor at /.well-known/oauth-protected-resource names https://app.circleci.com as its authorization server. No tool was called and no credential was supplied. · retrieved 2026-09-08Connect CircleCI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.