Skip to content

CI

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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which jobs failed on main in the last day?

Working in CircleCI with Elaichi

  • Get single CircleCI project by ID
  • List all CircleCI branches
  • List all CircleCI pipelines
Ask anything…
Governance / Audit log Last 24 hours
CircleCI List all CircleCI pipelines Emily Carter · ChatGPT · 9:41 AM Done
CircleCI List all CircleCI branches Emily Carter · ChatGPT · 9:41 AM Done
CircleCI Get single CircleCI project by ID Emily Carter · ChatGPT · 9:41 AM Done
CircleCI Get single CircleCI pipeline by ID Megan Brooks · Claude · 9:38 AM Done
CircleCI Create a CircleCI pipeline Ryan Hayes · Cursor · 9:35 AM Done

How to connect CircleCI to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

CircleCI MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ 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

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

CircleCI MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

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

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with CircleCI through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in CircleCI is logged.

  • Engineering

    Find out why the build went red

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

  • Release

    Approve a held deploy from chat

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

  • Platform

    Rerun a flaky workflow without hunting

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

  • Engineering management

    See which projects are slowing down

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

  • Support

    Confirm whether a fix has shipped

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

  • Security

    Know who kicked off a pipeline

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

Try asking

  • “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.”

See all 113 CircleCI tools →

What connecting CircleCI gets you

6 screens from Elaichi, each doing one job for your CircleCI account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask CircleCI why the build failed.

Three starter prompts answer from live pipelines, workflows and jobs, in plain language.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Use CircleCI from Claude, ChatGPT or Cursor.

One governed MCP endpoint connects them all, with no SDK and no shared API key.

ElaichiTools
Tool Action Description
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.

Tool catalog

113 CircleCI tools, ready without any code.

Pipelines, workflows, jobs, artifacts and insights, each listed with its resource and method.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

CircleCI · pipelines and jobs

CircleCI starter 18 Mar 4, 2026

Release toolbox

CircleCI · approvals and reruns

— 9 Mar 2, 2026

Platform toolbox

CircleCI · projects and workflows

— 24 Feb 27, 2026

QA toolbox

CircleCI · jobs and artifacts

CircleCI starter 6 Feb 19, 2026

Support toolbox

CircleCI · branches and pipeline status

— 31 Jan 30, 2026

Engineering management toolbox

CircleCI · insights and summaries

— 12 Jan 22, 2026

Toolboxes

Each team gets its own CircleCI toolbox.

Scope release, platform and support toolboxes to the work each team actually does.

ElaichiConnections
Connection Scope Status Access
CI

CircleCI (Core platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CI

CircleCI (Mobile)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CI

CircleCI (Web)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CI

CircleCI (Data)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CI

CircleCI (Release)

Connected by Ryan Hayes

Personal • Active Not shared
CI

CircleCI (Staging)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a CircleCI connection, never the key.

Teammates run pipelines through one connected account without ever seeing the API key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

CircleCI Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

CircleCI Pipelines Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

CircleCI Pipelines List Toolbox

Audit log

Know who reran, approved or canceled what.

Every CircleCI call is logged with who, when, what happened, type and resource.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

CircleCI digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch pipelines

    CircleCI

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    CircleCI

    Queued

Workflows

A schedule turns failed builds into action.

Failed CircleCI pipelines are fetched, grouped, drafted into a digest, approved, then posted.

CircleCI health

Refreshed 4 minutes ago · every 15 minutes · from the pipelines collection

Live

Pipelines

1,284 ↓ 12%

Workflows

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Pipelines created

Last 14 days

By team

Share of activity

Core platform 34%

Mobile 27%

Web 21%

Data 18%

Collections and dashboards

CircleCI health, computed without asking a model.

Four metrics, a 14 day pipelines chart and a team breakdown, refreshed on a schedule.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for CircleCI, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

CircleCI tools for your AI agents

113 tools are ready to call through Elaichi's MCP endpoint the moment you connect CircleCI, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put CircleCI in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot