# CI/CD MCP connectors for Claude, ChatGPT and Cursor 5+ CI/CD connectors in the Elaichi catalog, each callable through https://api.elaichi.ai/mcp once connected, under the same roles, restrictions and audit log as the rest of the catalog. Source: https://elaichi.ai/connectors/category/ci-cd/ | | | | --- | --- | | Category | CI/CD | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | ## CI/CD connectors - [Argo CD](https://elaichi.ai/connectors/argocd/) — 115 tools · hosted sign-in - [Codefresh](https://elaichi.ai/connectors/codefresh/) — 410 tools · hosted sign-in - [Hashicorp Terraform Cloud](https://elaichi.ai/connectors/hashicorpterraformcloud/) — 290 tools · hosted sign-in - [Render](https://elaichi.ai/connectors/render/) — 144 tools · hosted sign-in - [Vercel](https://elaichi.ai/connectors/vercel/) — 84 tools · hosted sign-in ## What teams do with CI/CD connectors ### Security - **Review admin accounts before a quarterly check** (Codefresh) — 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** (Hashicorp Terraform Cloud) — 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 has access to Render** (Render) — List the members of every Render workspace and check the roster against who is still on the team before an access review. ### Platform - **Find out why a deployment is stuck** (Argo CD) — 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. - **Pause a project that should not be live** (Vercel) — 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. - **Lock a workspace before a risky change** (Hashicorp Terraform Cloud) — 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 - **Check what a service is running** (Render) — 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** (Argo CD) — 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. - **Set up a new project with its variables** (Vercel) — 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 - **Onboard a new engineer in one ask** (Codefresh) — 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** (Hashicorp Terraform Cloud) — 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** (Argo CD) — 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 once it is 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) ## What an agent can call in CI/CD 1043 tools across the category. 5 of these connectors use hosted sign-in with nothing to register first; 0 ask you to bring your own OAuth app. ## 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. [Browse the full connector catalog](https://elaichi.ai/connectors/)