CircleCI

Official CircleCI Developer tools

Lets an agent review CircleCI execution details, log output, test information, and generated artifacts. Summary written by AI Index.

The registry’s description: CircleCI's MCP server: inspect projects, runs, workflows, jobs, logs, tests, and artifacts.

Remote server Needs a key: Authorization

Add to your client

Add the CircleCI MCP server to Claude Code

  1. Run the command

    claude mcp add --transport http circleci https://mcp.circleci.com/v1/mcp --header 'Authorization: <Authorization>'
  2. Fill in the values ↓

  3. Check it’s connected

If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for circleci in its list of MCP servers. A server that needs sign-in opens it on first use.

What you fill in

Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.

  • <Authorization> HTTP header Required · Secret

    OAuth 2.0 Bearer token

Client compatibility

By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.

Agent Skills: CircleCI

circleci-api, circleci-docs, circleci-mcp-server

Sources

This data comes from the Official MCP Registry.