Connect CircleCI to Claude Code
Read failed pipelines, workflows, jobs, test results and artifacts, and trigger, rerun or cancel CircleCI workflows. Add Toolspoke to Claude Code once and it can use 17 CircleCI actions. Your CircleCI credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install CircleCI and connect it
Add CircleCI to a project in your Toolspoke workspace.
Personal API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- Personal API token
- CircleCI → User Settings → Personal API Tokens → Create New Token. Project API tokens do not work with API v2. The token acts as you, with every permission you have in every organization you belong to.
Choose what Claude Code may do
All 17 actions start on. Switch off any of the 4 actions that change something in CircleCI, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the CircleCI actions that only read, so they are safe to try first.
- List the organizations the token's user belongs to, with the slug (e.g. gh/acme) that list_pipelines takes
- List recent pipelines across an organization, newest first
- List recent pipelines of one project, newest first, optionally on one branch
- Retrieve one pipeline by id, with its trigger, commit and any configuration errors
What Claude Code can do in CircleCI
13 actions read, 2 write and 2 delete or permanently change something.
Reads
List organizations
List the organizations the token's user belongs to, with the slug (e.g. gh/acme) that list_pipelines takes. A CircleCI personal token has no scopes, it either works or it does not, so this call is a complete connection test: if it returns the organization, every read below can reach it.
List pipelines
List recent pipelines across an organization, newest first. Use it to find the latest pipeline on a branch, then list_pipeline_workflows to see what failed.
List project pipelines
List recent pipelines of one project, newest first, optionally on one branch.
Get pipeline
Retrieve one pipeline by id, with its trigger, commit and any configuration errors.
List pipeline workflows
List the workflows of one pipeline with their status, failed, success, running, on_hold and so on.
Get workflow
Retrieve one workflow by id, with its status and timing.
List workflow jobs
List the jobs in one workflow with their status and job_number. An approval job's id here is the approval_request_id that approve_job takes.
Get job
Retrieve one job by project and job number, with its status, executor, duration and any messages CircleCI attached.
Get job steps
List one job's steps with each step's status, exit code and output_url. The output_url is a short-lived signed link to that step's log, readable without a token. Look for the step whose status is failed.
List job tests
List the test results one job stored with store_test_results, including each failure's message.
List job artifacts
List the artifacts one job stored, with each file's path and download URL.
Get flaky tests
List the tests CircleCI has seen both pass and fail on the same commit in this project, its flaky-test report.
Get workflow metrics
Summarize each workflow in a project over a reporting window, success rate, run count, duration percentiles and credits used.
Writes
Trigger pipeline
Start a new pipeline on a branch or tag. A write, not destructive, it adds a pipeline that cancel_workflow can stop, but it runs whatever the configuration runs, deploys included. Works for projects connected through the CircleCI OAuth app (gh/… and bb/… slugs); GitHub App projects need CircleCI's newer pipeline-run endpoint, which this connector does not declare.
Rerun workflow
Rerun a finished workflow, from the failed jobs only, or a chosen set of jobs, or from the start. It starts a new workflow; the old one is kept.
Deletes or permanently changes
Cancel workflow
Cancel a running workflow. Destructive because it cannot be undone, running jobs stop part-way, and the work can only be rerun from the start.
Approve job
Approve an on-hold approval job so the workflow continues. Destructive because an approval job is a human gate, often the one in front of a production deploy, and an approval cannot be withdrawn.
CircleCI in Claude Code: questions
Does Claude Code see my CircleCI credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in CircleCI?
Yes. Each of the 17 actions can be switched off for a project. Turn off the 4 that change something and Claude Code can only read.
Will 17 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the CircleCI action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a CircleCI call does not run in a sandbox, so it bills nothing.
CircleCI in your other apps
Try CircleCI in Claude Code
Free to start, and tool calls cost nothing on any plan.