DEVELOPMENT WORKFLOW / CircleCI
CircleCI MCP
Inspects CircleCI pipeline failures and performs explicitly authorized workflow actions through its hosted MCP service.
“This page walks through connecting an AI coding assistant to CircleCI’s hosted MCP server.”
01 / THE REASONING
Why this made the selection.
- Brings pipeline, test and failure context into the coding workflow through the official hosted service.
- Documents OAuth setup and a current tool list rather than relying on the deprecated standalone npm server.
- The page publishes a concrete endpoint (https://mcp.circleci.com/v1/mcp) rather than only a product name.
- The transport and any stated account requirement are specific enough to configure a client without guessing a second product.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Official hosted-server connection guide
- Official MCP overview and supported tools
- Documentation connecting-to-the-circleci-mcp-server
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.
Our findings
- The current guide explicitly separates hosted setup from the CircleCI CLI’s built-in MCP and the deprecated standalone npm server.
- The page documents the remote endpoint https://mcp.circleci.com/v1/mcp.
- That endpoint is documented with Streamable HTTP, not only as a local process.
- This page does not print individual tool names; it describes the endpoint, the sign-in path, or points elsewhere for the tool list.
- The publisher deprecates the former npx/PAT server in favor of hosted MCP and separately documents CircleCI CLI MCP.
Not established by this review
- No MCP server or upstream package was installed or run.
- No authenticated account, client handshake, query, write operation or security test was performed.
- The server was not installed or initialised.
- No tools/list or tool call was made.
- A source review is not a runtime or security certification.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
claude mcp add --transport http circleci-mcp-server https://mcp.circleci.com/v1/mcpCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- Add https://mcp.circleci.com/v1/mcp as a remote HTTP server and complete OAuth.
- Confirm project access and inspect the available tools.
- Start with pipeline inspection and review downstream effects before approving workflow actions.
Before you start
- A CircleCI account with access to the intended projects
- A compatible OAuth-capable remote MCP client
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"servers": {
"circleci-mcp-server": {
"type": "http",
"url": "https://mcp.circleci.com/v1/mcp"
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/
Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review
https://circleci.com/docs/guides/toolkit/circleci-mcp-overview/
Supports: review, limitations, access