Argo CD MCP connector
The Argo CD connector brings your applications, sync history, manifests and account tokens into Claude, ChatGPT, Cursor and the Elaichi Agent, so each engineer can ask about a deployment and act on it inside their own Argo CD access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
115 tools
How to connect
How to connect Argo CD to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Argo CD once
-
Open Connections, choose Add connection, and pick Argo CD.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Argo CD API key. One person generates a token in Argo CD and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Argo CD MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Argo CD MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Argo CD MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Argo CD to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Argo CD through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Platform
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.
-
DevOps
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.
-
SRE
Trace an incident to the resource
Walk the resource tree of an application to find the pod, service or config that changed, and read its events alongside the deployment timeline.
-
Engineering
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.
-
Release management
Stop a sync that is going wrong
Cancel a running operation on an application the moment it starts failing, then confirm the managed resources are back to a known state.
-
Security
Review accounts and rotate tokens
List every Argo CD account, check what each one is allowed to do, create a fresh token for a service account and delete the old one.
Try asking
- “Which Argo CD applications changed in the last day?”
- “List recent events for the payments Argo CD application.”
- “Show Argo CD accounts that hold active tokens.”
Compare
Elaichi vs Zapier MCP vs Composio for Argo CD
All three can connect Argo CD 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Argo CD tools | Allow or restrict single Argo CD 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 Argo CD 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 | $15 per user per month. | 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.
AI tools
Argo CD tools for your AI agents
115 tools are ready to call through Elaichi's MCP endpoint the moment you connect Argo CD, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Argo CD gets you
6 screens from the product, each doing one job for your Argo CD account.
The agent
Ask about Argo CD applications in plain language.
Answers come from live Argo CD applications, accounts and events, not stale exports.
- applications
- accounts
- tokens
- events
Ask Elaichi to work across your apps.
Which Argo CD applications changed in the last day?
List recent events for the payments Argo CD application.
Show Argo CD accounts that hold active tokens.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect Argo CD from any MCP client over OAuth, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
115 Argo CD tools land ready to call.
Applications, accounts, tokens and events are covered with no custom code to write.
- List all Argo CD accounts
- Argo CD accounts list 2
- Get single Argo CD account by ID
- List all Argo CD account can is
ElaichiToolsToolboxes
Every team gets its own Argo CD toolbox.
Platform, release and security teams each see the Argo CD tools their work needs.
- Platform
- Release engineering
- SRE
- Security
ElaichiToolboxesShared connections
Teammates use Argo CD without seeing credentials.
Each connection shows who linked the Argo CD account and which teams share it.
- Production
- Staging
- Platform core
- Payments cluster
ElaichiConnectionsAudit log
Every Argo CD call is on the record.
When, who, what happened, type and resource for each application and token action.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, an Argo CD digest ships.
Six steps fetch applications, group them, draft a digest, wait for approval, post back.
Argo CD digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch applications
Argo CD
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Argo CD
Queued
Collections and dashboards
Argo CD health arrives before anyone asks.
Four metrics, 14 days of applications created and a team breakdown, computed on schedule.
Argo CD health
Refreshed 4 minutes ago · every 15 minutes · from the applications collection
Applications
1,284 ↓ 12%
Accounts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Applications created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform core 21%
Payments cluster 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Argo CD to Claude?
Two steps. In Elaichi, choose Argo CD and paste in an API key from your Argo CD instance, 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 the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Argo CD is ready in that chat.
Does Argo CD work with ChatGPT and Cursor as well as Claude?
Yes. Once Argo CD is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Argo CD once and every client sees it.
What can an AI agent actually do with my Argo CD data?
It can list your Argo CD applications and tell you which are out of sync, read the events and logs for one that is failing, show the diff between the running state and the repository, and walk the resource tree down to the pod that changed. It can also create or update an application, cancel a running sync operation, and list accounts or create and delete tokens. Because Argo CD exposes more than a hundred actions, short specific asks such as "show events for the payments app" work better than long paragraphs.
Does connecting Argo CD give the AI access to every cluster and project?
No. The agent works inside the Argo CD permissions of the API key and the person who signed in, so if that person cannot see a project or cluster in Argo CD, neither can the agent. Elaichi can narrow that access further with restrictions, and it never widens it beyond what Argo CD already allows.
Can I stop an agent from deleting or changing things in Argo CD?
Yes. Restrictions in Elaichi work per action, so you can allow reading Argo CD applications, events, logs and diffs while blocking creating, updating or deleting applications and tokens. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, accidental or otherwise, can reach it.
What happens to an Argo CD connection when someone leaves?
Offboarding that person in Elaichi ends their access to Argo CD through every client at once, and the audit log keeps their history. A shared Argo CD connection keeps working for everyone else on the team. If you want to remove Argo CD entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the Argo CD MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Argo CD 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, 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 Argo CD?
Yes. Both let Claude, ChatGPT or Cursor use Argo CD. 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 Argo CD call.
How is Elaichi different from Composio for Argo CD?
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 Argo CD: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Argo CD in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.