# CircleCI MCP connector

Connect CircleCI to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can check pipelines, rerun workflows, approve holds and read build insights, each person inside their own CircleCI access, every call logged.

Source: https://elaichi.ai/connectors/circleci/

## Facts

| | |
| --- | --- |
| Application | CircleCI |
| Category | CI |
| AI tools | 113 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once CircleCI is connected

- Which jobs failed on main in the last day?
- Rerun the last failed workflow for the checkout service.
- Show build success rate and duration for the API project this month.

## Connect CircleCI in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick CircleCI.
2. Optionally set Share with, then press Connect.
3. Paste a CircleCI API key. One person generates a token in CircleCI and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which CircleCI tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## CircleCI MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## CircleCI MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## CircleCI MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## CircleCI MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## CircleCI MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect CircleCI to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a CircleCI tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with CircleCI through Elaichi

### Find out why the build went red

Engineering. Ask which job failed on the main branch and pull up the artifacts it left behind, without opening six tabs in CircleCI.

### Approve a held deploy from chat

Release. When a workflow is waiting on approval, ask for the pipeline details and approve it, or cancel it, from the same conversation.

### Rerun a flaky workflow without hunting

Platform. Ask for the last failed workflow on a project and rerun it, or start a fresh pipeline on a branch when a fix lands.

### See which projects are slowing down

Engineering management. Pull insights summaries for one project or the whole organization to spot rising durations and falling success rates before sprint planning.

### Confirm whether a fix has shipped

Support. Check whether the pipeline for a branch finished and which jobs ran, so you can give a customer a straight answer.

### Know who kicked off a pipeline

Security. Look up who triggered a pipeline and when, then cancel anything that should not be running.

## Elaichi vs Zapier MCP vs Composio for CircleCI

All three can connect CircleCI to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over CircleCI tools | Allow or restrict single CircleCI tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per CircleCI call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect CircleCI to Claude?

Connect CircleCI in Elaichi by pasting a CircleCI API key, which takes about a minute. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and CircleCI is ready to use in Claude.

### Does CircleCI work with ChatGPT and Cursor as well as Claude?

Yes. Once CircleCI is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect CircleCI once and every client picks it up.

### What can an AI agent actually do with my CircleCI data?

It can list your CircleCI projects, branches and pipelines, tell you which workflows and jobs passed or failed, and fetch the artifacts a job produced. It can start a pipeline on a branch, rerun a workflow, approve a held workflow, cancel a running job, and read insights on duration and success rates for a project or the whole organization. Short, concrete asks such as "rerun the last failed workflow on checkout" work better than long paragraphs.

### Does connecting CircleCI give the AI access to every project in my organization?

No. An agent only sees the CircleCI projects, pipelines and organizations that the person who signed in can already see, because every call runs inside that person's own access. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond what CircleCI already allows.

### Can my team share one CircleCI connection?

Yes. One person connects CircleCI with their API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who reran a workflow or approved a deploy.

### Can I stop an agent from deleting or changing things in CircleCI?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting a CircleCI project, cancelling jobs or starting pipelines for a role or for one person while leaving read access alone. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a CircleCI connection when someone leaves?

Offboarding a person in Elaichi ends their CircleCI access through every client at once. A shared CircleCI connection keeps working for everyone else on the team. If you want CircleCI gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

### Does the CircleCI MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. CircleCI is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for CircleCI?

Yes. Both let Claude, ChatGPT or Cursor use CircleCI. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every CircleCI call.

### How is Elaichi different from Composio for CircleCI?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to CircleCI: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 113 CircleCI tools

Every tool below is callable through https://api.elaichi.ai/mcp once CircleCI is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single CircleCI project by ID** (Get). Get a project. Returns: slug, name, id, organization_name, organization_slug, organization_id, vcs_info. Required: id.
- **Delete a CircleCI project by ID** (Delete). Delete a project. Returns: message. Required: id.
- **List all CircleCI branches** (List). Get all branches for a project. Returns: org_id, project_id, branches. Required: project_slug.
- **List all CircleCI pipelines** (List). Get a list of pipelines. Returns: id, errors, project_slug, updated_at, number, trigger_parameters, state, created_at, warnings, trigger.
- **Get single CircleCI pipeline by ID** (Get). Get a pipeline by ID. Returns: id, errors, project_slug, updated_at, number, trigger_parameters, state, created_at, warnings, trigger. Required: id.
- **Create a CircleCI pipeline** (Create). Trigger a new pipeline. Returns: id, state, number, created_at. Required: project_slug.
- **Get single CircleCI user by ID** (Get). User Information. Returns: avatar_url, id, login, name. Required: id.
- **List all CircleCI project pipelines** (List). Get all pipelines. Returns: id, errors, project_slug, updated_at, number, trigger_parameters, state, created_at, warnings, trigger. Required: project_slug.
- **Get single CircleCI project pipeline by ID** (Get). Get a pipeline by pipeline number. Returns: id, errors, project_slug, updated_at, number, trigger_parameters, state, created_at, warnings, trigger. Required: project_slug, id.
- **List all CircleCI workflows** (List). Get a pipeline's workflows. Returns: pipeline_id, canceled_by, id, auto_rerun_number, name, project_slug, errored_by, tag, status, started_by. Required: pipeline_id.
- **Get single CircleCI workflow by ID** (Get). Get a workflow. Returns: pipeline_id, canceled_by, id, auto_rerun_number, name, project_slug, errored_by, tag, status, started_by. Required: id.
- **CircleCI workflows cancel** (Cancel). Cancel a workflow. Returns: message. Required: workflow_id.
- **List all CircleCI jobs** (List). Get a workflow's jobs. Returns: canceled_by, dependencies, job_number, id, started_at, name, approved_by, project_slug, status, type. Required: workflow_id.
- **Get single CircleCI job by ID** (Get). Get details of a single job in a project by job number, including status, timings, executor, parallel runs, and the latest workflow and pipeline. Returns: created_at, duration, executor, messages, queued_at, started_at, status, stopped_at, parallel_runs, contexts. Required: project_slug, id (the job number).
- **CircleCI jobs cancel** (Cancel). Cancel a running job in a project by its job number. Returns: message. Required: project_slug, job_number.
- **List all CircleCI job artifacts** (List). List the artifacts produced by a project's job, with each artifact's path, node index, and download URL. Returns: path, node_index, url. Required: project_slug, job_number.
- **List all CircleCI current users** (List). User Information. Returns: avatar_url, id, login, name.
- **List all CircleCI collaborations** (List). Collaborations. Returns: id, vcs-type, name, avatar_url, slug.
- **Create a CircleCI workflow approval** (Create). Approve a job. Returns: message. Required: workflow_id, job_id.
- **Create a CircleCI workflow rerun** (Create). Rerun a workflow. Returns: workflow_id. Required: workflow_id.
- **Create a CircleCI pipeline continuation** (Create). Continue a pipeline. Returns: message.
- **List all CircleCI insights project summaries** (List). Get summary metrics and trends for a project across it's workflows and branches. Returns: org_id, project_id, project_data, project_workflow_data, project_workflow_branch_data, all_branches, all_workflows. Required: project_slug.
- **List all CircleCI insights job timeseries** (List). Job timeseries data. Returns: name, min_started_at, max_ended_at, timestamp, metrics. Required: project_slug, workflow_name.
- **List all CircleCI insights org summaries** (List). Get summary metrics with trends for the entire org, and for each project. Returns: org_data, org_project_data, all_projects. Required: org_slug.
- **List all CircleCI insights flaky tests** (List). Get flaky tests for a project. Returns: flaky-tests, total-flaky-tests. Required: project_slug.
- **List all CircleCI insights workflows** (List). Get summary metrics for a project's workflows. Returns: name, metrics, window_start, window_end, project_id. Required: project_slug.
- **List all CircleCI insights workflow runs** (List). Get recent runs of a workflow. Returns: id, branch, duration, created_at, stopped_at, credits_used, status, is_approval. Required: project_slug, workflow_name.
- **List all CircleCI insights workflow jobs** (List). Get summary metrics for a project workflow's jobs. Returns: name, metrics, window_start, window_end. Required: project_slug, workflow_name.
- **List all CircleCI insights workflow summaries** (List). Get metrics and trends for workflows. Returns: metrics, trends, workflow_names. Required: project_slug, workflow_name.
- **List all CircleCI insights workflow test metrics** (List). Get test metrics for a project's workflows. Returns: average_test_count, most_failed_tests, most_failed_tests_extra, slowest_tests, slowest_tests_extra, total_test_runs, test_runs. Required: project_slug, workflow_name.
- **CircleCI job runs cancel** (Cancel). Cancel job by job ID. Returns: message. Required: job_id.
- **Get single CircleCI job run by ID** (Get). Get a job. Returns: id, name, job_number, type, status, project_id, pipeline_id, workflow_id, started_at, stopped_at. Required: id.
- **Create a CircleCI organization** (Create). Create a new organization. Returns: id, name, slug, vcs_type, avatar_url.
- **Delete a CircleCI organization by ID** (Delete). Delete an organization. Returns: message. Required: id.
- **Get single CircleCI organization by ID** (Get). Get an organization. Returns: id, name, slug, vcs_type, avatar_url. Required: id.
- **Create a CircleCI organization project** (Create). Create a new project. Returns: slug, name, id, organization_name, organization_slug, organization_id, vcs_info. Required: org_slug_or_id.
- **List all CircleCI URL orb allow lists** (List). List the entries in the org's URL Orb allow-list. Returns: id, name, prefix, auth. Required: org_slug_or_id.
- **Create a CircleCI URL orb allow list** (Create). Create a new URL Orb allow-list entry. Returns: id, message. Required: org_slug_or_id.
- **Delete a CircleCI URL orb allow list by ID** (Delete). Remove an entry from the org's URL orb allow-list. Returns: id, message. Required: org_slug_or_id, id.
- **Get single CircleCI pipeline config by ID** (Get). Get a pipeline's configuration. Returns: source, compiled, setup-config, compiled-setup-config. Required: id.
- **List all CircleCI pipeline values** (List). Get pipeline values for a pipeline. Required: pipeline_id.
- **List all CircleCI checkout keys** (List). Get all checkout keys. Returns: public-key, type, fingerprint, preferred, created-at. Required: project_slug.
- **Create a CircleCI checkout key** (Create). Create a new checkout key. Returns: public-key, type, fingerprint, preferred, created-at. Required: project_slug.
- **Delete a CircleCI checkout key by ID** (Delete). Delete a checkout key. Returns: message. Required: project_slug, id.
- **Get single CircleCI checkout key by ID** (Get). Get a checkout key. Returns: public-key, type, fingerprint, preferred, created-at. Required: project_slug, id.
- **Create a CircleCI project env var** (Create). Create an environment variable. Returns: name, value, created-at. Required: project_slug.
- **List all CircleCI project env vars** (List). List all environment variables. Returns: name, value, created-at. Required: project_slug.
- **Get single CircleCI project env var by ID** (Get). Get a masked environment variable. Returns: name, value, created-at. Required: project_slug, id.
- **Delete a CircleCI project env var by ID** (Delete). Delete an environment variable. Returns: message. Required: project_slug, id.
- **List all CircleCI my project pipelines** (List). Get your pipelines. Returns: id, errors, project_slug, updated_at, number, trigger_parameters, state, created_at, warnings, trigger. Required: project_slug.
- ...and 63 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
