--- title: "CircleCI MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/circleci/ description: "Inspects CircleCI pipeline failures and performs explicitly authorized workflow actions through its hosted MCP service." --- # CircleCI MCP: review, setup & limitations · Undominated.ai > Inspects CircleCI pipeline failures and performs explicitly authorized workflow actions through its hosted MCP service. [← Explore all mcp servers](/mcp-servers/) DEVELOPMENT WORKFLOW / CircleCI # CircleCI MCP Inspects CircleCI pipeline failures and performs explicitly authorized workflow actions through its hosted MCP service. [See setup guidance ↓](#setup)[Original source ↗](https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/) SOURCE REVIEW Reviewed 2026-10-14 Evidence 2 linked sources Publisher CircleCI Licence Not established [Read what was—and wasn’t—checked ↓](#review) “This page walks through connecting an AI coding assistant to CircleCI’s hosted MCP server.” [CircleCI · upstream description ↗](https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/) Our analysis follows below. 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. ### A good fit for - Investigating a failed build with its workflow and test context - Connect a client to the endpoint on this page and inspect the live tool list before relying on a tool name. - Match the credentials and transport on this page, and do not treat unstated tools as available. ### Weigh up before choosing - Workflow tools can retry or cancel work; rerun repository CI jobs may deploy or otherwise change external systems. - The previously published standalone npm setup is deprecated. This entry selects the current hosted endpoint. - Account permissions, project visibility and organization policy still apply; logs can contain sensitive data. - Individual tool names were not on the fetched page, so this review does not invent them. - This review did not start the server or call its tools. - The hosted server and CLI MCP are separate integrations; keeping the obsolete registration can expose duplicate or stale tools. 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. [Upstream setup instructions ↗](https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/) DOCUMENTED COMMAND claude mcp add --transport http circleci-mcp-server https://mcp.circleci.com/v1/mcp Copy command ↗ Copying 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" } } } Copy configuration ↗ ### Compatibility Claude Code · Remote MCP clients ### Transports Streamable HTTP ### Hosted account connection - Read permitted pipeline, job, log and test information - Perform available workflow actions with the connected CircleCI user’s permissions - Network access to https://mcp.circleci.com/v1/mcp ### Cost model Hosted CircleCI account and job usage terms apply; triggered work may consume compute credits. Assistant usage is separate. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Official setup and capabilities ↗](https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/) Checked 2026-10-14 https://circleci.com/docs/guides/toolkit/connecting-to-the-circleci-mcp-server/ Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review - [Official CircleCI MCP overview and tools ↗](https://circleci.com/docs/guides/toolkit/circleci-mcp-overview/) Checked 2026-10-14 https://circleci.com/docs/guides/toolkit/circleci-mcp-overview/ Supports: review, limitations, access KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Buildkite MCP server ↗ Exposes Buildkite pipelines, builds, jobs, and tests to an MCP client, locally or through Buildkite's remote server.](/mcp-servers/buildkite-mcp-server/)[### Postman MCP ↗ Connects assistants to Postman collections, workspaces and environments through selectable tool sets.](/mcp-servers/postman/)[### Apollo MCP Server ↗ Exposes a chosen set of GraphQL operations as MCP tools backed by an existing graph.](/mcp-servers/apollo/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Inspect resource evidence](/tools/) - [Choose a host](/agents/) - [Inspect reusable workflows](/skills/) - [Use Undominated data](/api/)