Skip to content

Connectors / CI/CD

CI/CD MCP connectors for Claude, ChatGPT and Cursor

5+ CI/CD connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

Start 14-day free trial Browse the full catalog
https://api.elaichi.ai/mcp The same for every user.

  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

CI/CD connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

5 connectors

Browse all 500+ connectors →

In practice

What teams do with CI/CD connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Security

  • Codefresh

    Review admin accounts before a quarterly check

    List every Codefresh admin, spot the people who no longer need that level of access, and remove them in one batch.

  • Hashicorp Terraform Cloud

    Review who belongs to which team

    List every team in a Hashicorp Terraform Cloud organization and see the details of each before an access review, without clicking through the console one team at a time.

  • Render

    Review who has access to Render

    List the members of every Render workspace and check the roster against who is still on the team before an access review.

Platform

  • Argo CD

    Find out why a deployment is stuck

    Ask which applications are out of sync or degraded, then pull the recent events and logs for the one that matters without opening Argo CD.

  • Vercel

    Pause a project that should not be live

    Pause a Vercel project that is no longer needed, is running up usage, or is misbehaving, then confirm which projects on the team are still active.

  • Hashicorp Terraform Cloud

    Lock a workspace before a risky change

    Ask the agent to lock a Hashicorp Terraform Cloud workspace while you investigate a problem, then unlock it once the change is safe. Nobody can queue a run against it in the meantime.

Engineering

  • Render

    Check what a service is running

    Ask which services live in a Render workspace and pull up one service's settings, region and connected repository without opening the Render dashboard.

  • Argo CD

    Register a new application from a template

    Create an Argo CD application for a new service with the right repository, path and destination cluster, and update it later when the branch or namespace changes.

  • Vercel

    Set up a new project with its variables

    Create a Vercel project for a new site or service and add the environment variables it needs in one conversation, instead of clicking through the settings pages one field at a time.

DevOps

  • Codefresh

    Onboard a new engineer in one ask

    Add the engineer to the Codefresh account, resend the invite if it was missed, and attach the right team rule without opening the admin console.

  • Hashicorp Terraform Cloud

    Spin up a workspace for a new service

    Create a Hashicorp Terraform Cloud workspace with the right name and settings when a team starts a new project, and assign the SSH key it needs to pull private modules.

  • Argo CD

    Check the diff before you approve a sync

    See the server side diff between what is running and what the repository says should be running, and describe the change in plain words for the release channel.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the CI/CD account you connected.

  • Which Argo CD applications changed in the last day?

    Argo CD

  • List every Codefresh admin and when they were added

    Codefresh

  • Which workspaces in the platform organization are currently locked?

    Hashicorp Terraform Cloud

  • Which Render blueprints changed in the last week?

    Render

  • List Vercel projects created this week and their owners.

    Vercel

The tools

What an agent can call in CI/CD

Connectors
5+

in the CI/CD catalog

Tools
1,043

callable the moment you connect

Hosted sign-in
5

connect with nothing to register

Of those 1,043 tools, 12% delete something. Restricting an agent to reads is not a promise here, it is 450 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 43%
450 tools · list, get, search
Write 31%
319 tools · create, update, send
Delete 12%
123 tools · delete, remove, archive
Other 14%
151 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every CI/CD connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

CI/CD connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Codefresh 410 Hosted
Hashicorp Terraform Cloud 290 Hosted
Render 144 Hosted
Argo CD 115 Hosted
Vercel 84 Hosted

FAQ

Frequently asked questions

How many CI/CD connectors does Elaichi have?

5+ CI/CD connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use CI/CD connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a CI/CD account once makes it reachable from every one of them.

Do CI/CD connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. CI/CD connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do CI/CD connectors need me to bring my own OAuth app?

No. Every CI/CD connector in the catalog connects through Elaichi's hosted sign-in, so there is nothing to register before you start.

Can I stop an agent from writing to CI/CD tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a CI/CD connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared CI/CD connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Put CI/CD connectors in front of your team

14 days on Gold, no credit card. Connect one and pick what each team can call.

Start free trial Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.