Skip to content

Connectors / CI/CD

CI/CD MCP connectors for Claude, ChatGPT, Cursor and Microsoft Copilot

Elaichi connects your team’s AI to 5+ CI/CD apps. Each person’s AI can do only what they’re allowed to, and every action it takes in your apps is logged.

  • Free 14-day trial
  • No credit card
  • Free plan for one person

CI/CD connectors in the catalog

Connect one, share it with your team, and each person’s AI can do only what they’re allowed to. Nobody has to hand a login around.

7 connectors

Browse all 650+ connectors →

What teams do with CI/CD connectors

Ask in plain English. Your AI does the work in the CI/CD apps your team already uses.

Engineering

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

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

  • Open a pull request from a plain request

    Describe the change you want and the agent creates the branch, updates the file and opens the pull request for review. You stay in the conversation while the work lands in GitHub under your name.

Security

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

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

  • Review who can reach which project

    List every Vercel member and every project member across your teams to spot people with more access than their job needs, and remove access that should not be there.

Platform

  • Check which agents are online before a release

    Ask which agents are connected to a cluster and what they are running right now. Spot a queue with nothing picking up jobs before the release train reaches it.

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

  • Stand up a new service from chat

    Describe the web service or background worker you need and have it created in Render, then adjust its settings later as the plan changes.

DevOps

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

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

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

Things to ask

Ask from ChatGPT, Claude, Cursor or Microsoft Copilot. Each person’s AI can do only what they’re allowed to.

  • Which Argo CD applications changed in the last day?

    Argo CD

  • Which agents are online in the production cluster right now?

    Buildkite

  • List every Codefresh admin and when they were added

    Codefresh

  • Open a pull request that fixes the typo in README

    GitHub

  • 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

For IT and engineering

What an agent can call in CI/CD

5+ CI/CD connectors bring 1,183 tools you can call the moment you connect, and 2 of the connectors sign in with nothing to register.

Of those 1,183 tools, 10% delete something. Switch off the delete tools for a role or one person, and their AI can’t use them.

Read 44%
526 tools · list, get, search
Write 29%
341 tools · create, update, send
Delete 10%
123 tools · delete, remove, archive
Other 16%
193 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector on this page answers here.

Every CI/CD connector, by depth

Tool counts are what each connector exposes; the split is what those tools do. Hosted means you sign in with nothing to register. Your own app means an admin adds your OAuth app for the connector once, then you connect. API key and App credentials mean an admin pastes them once, with nothing to register.

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

Questions, answered

How many CI/CD connectors does Elaichi have?

5+ CI/CD connectors are in the catalog. Each one arrives as a set of MCP tools an agent can call through Elaichi’s one MCP endpoint.

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

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. 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, Microsoft Copilot 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. 2 of the CI/CD connectors use Elaichi's hosted sign-in, with nothing to register. 5 connect with an API key or app credentials that an admin pastes once, with no app to register. Nothing in this category asks you to register an OAuth app 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 can't be used by the people it is restricted for. 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 of Black, no credit card. Connect one 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