CircleCI CLI

circleci-cli

The official CircleCI CLI shows runs and failing-test logs, while skills and MCP connect it to Claude Code, Codex and Cursor.

  • 460 ★ on the repository
  • Last commit
  • MIT
CLIOfficial

Extended access

Why this level

  • Uses your CircleCI token and can rerun jobs
  • Hands build logs to the agent, which can contain secrets and internal addresses
All reasons and checks

circleci-public/circleci-cli

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add cli/circleci-cli

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Uses your CircleCI token and can rerun jobs
  • Hands build logs to the agent, which can contain secrets and internal addresses

This is third-party code. Review the repository files before installing.

What it does

`circleci` is the CircleCI command-line tool for runs, jobs and configuration straight from the terminal. The README calls it an agent-friendly CLI. For Claude Code and Codex, CircleCI publishes dedicated skills in the `CircleCI-Public/skills` repository: they teach an agent to validate configuration, watch a run, read failing job and test logs, and rerun jobs. `circleci help agents` prints the steps. The CLI can also enable MCP for Claude desktop, Cursor and VS Code with `circleci mcp <client> enable` commands.

Who it is for. Teams whose builds run on CircleCI at circleci.com or CircleCI server and who want to triage failed pipelines without leaving an agent chat.

Good fit when

  • A pipeline failed and an agent has to read job logs and find the failing test.
  • Before a push the `.circleci/config.yml` configuration should be validated from the terminal.
  • A run needs watching and a job needs a rerun after a fix.
  • Cursor or VS Code has to be connected to CircleCI through MCP with one command.

Not a fit when

  • Builds run in another CI: the CLI works only with CircleCI.
  • An agent must not be trusted with a CircleCI token: the CLI works with a token after `circleci auth login`.
  • A replacement for the web UI in project setup is expected: the CLI focuses on runs and configuration.

Example request

Show the latest pipeline run, find the failed job, read the test logs and suggest a fix without rerunning.

Limitations

After `circleci auth login` the CLI works with your token and the agent acts on your behalf. The skills live in a separate `CircleCI-Public/skills` repository, not in the CLI itself. Installing skills for Cursor goes through `npx skills add` and needs Node 22.20 or newer. Rerunning jobs may spend credits on your CircleCI plan. The full command list and MCP connection options are documented at cli.circleci.com, while the README covers only the main ones.

How to disable. Remove the `circleci` plugin in Claude Code or Codex, run `circleci mcp <client> disable` if MCP was enabled, and uninstall the CLI with the package manager used for installing. Delete the stored token from CLI settings.

FAQ

How do I install the skills for different agents?

For Claude Code: `claude plugin marketplace add CircleCI-Public/skills`, then `claude plugin install circleci@circleci-public-skills`. For Codex: `codex plugin marketplace add CircleCI-Public/skills` and `codex plugin add circleci@circleci-skills`.

What about Cursor?

Run `npx skills add CircleCI-Public/skills -a cursor --skill circleci-cli`. Without Node, copy the skill folder into `~/.cursor/skills/<name>` by hand.

How do I enable MCP?

`circleci mcp claude enable` for Claude desktop followed by `claude mcp add-from-claude-desktop -s user`, `circleci mcp cursor enable` for Cursor and `circleci mcp vscode enable` for VS Code.

Which CLI install methods exist?

Homebrew (`brew install circleci`), winget on Windows, snap, plus apt, yum and dnf packages on Linux.

Does the CLI work with CircleCI server?

Yes, the README states support for both circleci.com and CircleCI server on macOS, Windows and Linux.

Discussion

No questions or reviews yet.

CLI tools
Official

JetBrains' official TeamCity CLI: start builds, tail logs, check the queue and shell into an agent from a terminal.

CLIBroad access130Repository stars
Official

The official Coralogix CLI with 19 skills: an agent reads production logs, traces and metrics and triages incidents

CLIBroad access241Repository stars

Docker Skills

docker-skills

Official

Official Docker skills for agents: Dockerfile and builds, Compose, Sandboxes, Docker Agent and a skill that confirms irreversible actions

SkillMinimal access616Repository stars

Claude Code Tools

claude-code-tools

A set of practical tools for Claude Code, Codex CLI and similar agents: utilities, skills, agents, hooks and plugins for terminal work

CLIExtended access2KRepository stars

A CLI and Kubernetes operator that runs Claude Code, Codex, Gemini, OpenCode and Cursor as tasks and sessions inside a cluster

CLIBroad access354Repository stars

31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker

SkillExtended access332Repository stars

README in short

The README opens with CLI installation, then gives skills and MCP commands in separate blocks. The `circleci help agents` section repeats the agent steps right in the terminal.

README badge

Report a problem

Foxx AICircleCI CLI
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.