Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect CircleCI to Claude Code

Let Claude rerun failed workflows and trigger pipelines in CircleCI. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect CircleCI to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect CircleCI, you add a CircleCI MCP server: a small hosted service that exposes CircleCI's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own CircleCI account. No API keys pasted into config files.

claude mcp add --transport http circleci https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in CircleCI once connected?

Full read-write CircleCI access lets Claude rerun a failed workflow, trigger a pipeline on a branch, cancel a stuck job, and update environment variables once you approve. The build babysitting and rerun-after-flake loops that used to mean tab-switching happen where the pipeline already runs.

  • Rerun a failed workflow, optionally from the failed job onward
  • Trigger a new pipeline on a specified branch or tag
  • Cancel a running or stuck workflow
  • Add or update a project environment variable after you approve
  • Approve a held job in a workflow that is waiting on a gate
  • Surface the failing step's logs and propose the rerun

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same CircleCI access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the CircleCI API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when CircleCI changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build CircleCI connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same CircleCI connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own CircleCI account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on CircleCI's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to CircleCI?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the CircleCI account it signs in with. Revoking access is one click in CircleCI.

More on the CircleCI connector

CircleCI connector for claude.aiBitbucket + Claude CodeJenkins + Claude CodeVercel + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us