# Argo CD MCP connector

The Argo CD connector brings your applications, sync history, manifests and account tokens into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each engineer can ask about a deployment and act on it inside their own Argo CD access.

Source: https://elaichi.ai/connectors/argocd/

## Facts

| | |
| --- | --- |
| Application | Argo CD |
| Category | CI |
| AI tools | 115 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Argo CD is connected

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

## Connect Argo CD in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Argo CD.
2. Optionally set Share with, then press Connect.
3. 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Argo CD tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Argo CD MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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 Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## Argo CD MCP connector for ChatGPT

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Argo CD MCP connector for Cursor

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Argo CD MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Argo CD to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Argo CD tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Argo CD through Elaichi

### Find out why a deployment is stuck

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

### Check the diff before you approve a sync

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

### Trace an incident to the resource

SRE. Walk the resource tree of an application to find the pod, service or config that changed, and read its events alongside the deployment timeline.

### Register a new application from a template

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

### Stop a sync that is going wrong

Release management. Cancel a running operation on an application the moment it starts failing, then confirm the managed resources are back to a known state.

### Review accounts and rotate tokens

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

## 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. Endpoint: 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 | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, Microsoft Copilot, 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 my team share one Argo CD connection?

Yes. One person connects Argo CD in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every action in Argo CD is recorded against the person who asked for it, not against the person who connected it.

### 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 restricting creating, updating or deleting applications and tokens. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

### 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, Microsoft Copilot 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, 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 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.

## All 115 Argo CD tools

Every tool below is callable through https://api.elaichi.ai/mcp once Argo CD is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Argo CD accounts** (List). Returns the list of accounts. Returns: items.
- **Argo CD accounts list 2** (List). Returns an account. Returns: capabilities, enabled, name, tokens. Required: name.
- **Get single Argo CD account by ID** (Get). Returns an account. Returns: capabilities, enabled, name, tokens. Required: id.
- **List all Argo CD account can is** (List). Checks if the current account has permission to perform an action. Returns: value. Required: resource, action, subresource.
- **Update a Argo CD account password by ID** (Update). Updates an account's password to a new value.
- **Create a Argo CD token** (Create). Creates a token. Returns: token. Required: name.
- **Delete a Argo CD token by ID** (Delete). Deletes a token. Required: id, name.
- **List all Argo CD applications** (List). List returns list of applications. Returns: items, metadata.
- **Create a Argo CD application** (Create). Create creates an application. Returns: metadata, operation, spec, status.
- **Update a Argo CD application by ID** (Update). Update updates an application. Returns: metadata, operation, spec, status. Required: id.
- **Get single Argo CD application by ID** (Get). Get returns an application by name. Returns: metadata, operation, spec, status. Required: id.
- **Argo CD applications update 2** (Update). Patch patch an application. Returns: metadata, operation, spec, status. Required: name.
- **Delete a Argo CD application by ID** (Delete). Delete deletes an application. Returns: metadata, operation, spec, status. Required: id.
- **Argo CD applications list events** (List). Returns a list of event resources. Returns: items, metadata. Required: name.
- **Argo CD applications list logs** (List). Returns stream of log entries for the specified pod. Pod. Returns: error, result. Required: name.
- **Argo CD applications partial update** (Update). Patch patch an application. Returns: metadata, operation, spec, status. Required: id.
- **Create a Argo CD applications manifests with file** (Create). Returns application manifests using provided files to generate them. Returns: commands, manifests, namespace, revision, server, sourceType, verifyResult.
- **List all Argo CD application server side diffs** (List). Performs server-side diff calculation using dry-run apply. Returns: items, modified. Required: app_name.
- **List all Argo CD application managed resources** (List). Returns list of managed resources. Returns: items. Required: application_name.
- **List all Argo CD application resource trees** (List). Returns resource tree. Returns: hosts, nodes, orphanedNodes, shardsCount. Required: application_name.
- **Argo CD application resource trees list 2** (List). Watch returns stream of application resource tree. Returns: error, result. Required: application_name.
- **List all Argo CD application links** (List). Returns the list of all application deep links. Returns: items. Required: name.
- **List all Argo CD application manifests** (List). Returns application manifests. Returns: commands, manifests, namespace, revision, server, sourceType, verifyResult. Required: name.
- **Delete a Argo CD application operation by ID** (Delete). Terminates the currently running operation. Required: name.
- **List all Argo CD application pods** (List). Returns stream of log entries for the specified pod. Pod. Returns: error, result. Required: name, pod_name.
- **List all Argo CD application resources** (List). Returns single application resource. Returns: manifest. Required: name.
- **Create a Argo CD application resource** (Create). Patch single application resource. Returns: manifest. Required: name.
- **Delete a Argo CD application resource by ID** (Delete). Deletes a single application resource. Returns: metadata, operation, spec, status. Required: name.
- **List all Argo CD resource actions** (List). Returns list of resource actions. Returns: actions. Required: name.
- **Create a Argo CD resource action** (Create). Runs a resource action. Returns: metadata, operation, spec, status. Required: name.
- **Argo CD resource actions create 2** (Create). Runs a resource action with parameters. Returns: metadata, operation, spec, status. Required: name.
- **List all Argo CD resource links** (List). Returns the list of all resource deep links. Returns: items. Required: name.
- **List all Argo CD revision chartdetails** (List). Get the chart metadata (description, maintainers, home) for a specific revision of the application. Returns: description, home, maintainers. Required: name, revision.
- **List all Argo CD metadata** (List). Get the meta-data (author, date, tags, message) for a specific revision of the application. Returns: author, date, message, references, signatureInfo, tags. Required: name, revision.
- **List all Argo CD revision ocimetadatas** (List). Get the chart metadata (description, maintainers, home) for a specific revision of the application. Returns: authors, createdAt, description, docsUrl, imageUrl, sourceUrl, version. Required: name, revision.
- **Create a Argo CD application rollback** (Create). Rollback syncs an application to its target state. Returns: metadata, operation, spec, status. Required: name.
- **Update a Argo CD application spec by ID** (Update). Updates an application spec. Returns: destination, ignoreDifferences, info, project, revisionHistoryLimit, source, sourceHydrator, sources. Required: name.
- **Create a Argo CD application sync** (Create). Sync syncs an application to its target state. Returns: metadata, operation, spec, status. Required: name.
- **List all Argo CD application syncwindows** (List). Get returns sync windows of the application. Returns: activeWindows, assignedWindows, canSync. Required: name.
- **List all Argo CD applicationsets** (List). List returns list of applicationset. Returns: items, metadata.
- **Create a Argo CD applicationset** (Create). Create creates an applicationset. Returns: metadata, spec, status.
- **Get single Argo CD applicationset by ID** (Get). Get returns an applicationset by name. Returns: metadata, spec, status. Required: id.
- **Delete a Argo CD applicationset by ID** (Delete). Delete deletes an application set. Returns: applicationset, project. Required: id.
- **Argo CD applicationsets list events** (List). Returns a list of event resources. Returns: items, metadata. Required: name.
- **Create a Argo CD applicationsets generate** (Create). Generate generates. Returns: applications.
- **List all Argo CD applicationset resource trees** (List). Returns resource tree. Returns: nodes. Required: name.
- **List all Argo CD certificates** (List). List all available repository certificates. Returns: items, metadata.
- **Create a Argo CD certificate** (Create). Creates repository certificates on the server. Returns: items, metadata.
- **Delete a Argo CD certificate by ID** (Delete). Delete the certificates that match the RepositoryCertificateQuery. Returns: items, metadata.
- **List all Argo CD clusters** (List). List returns list of clusters. Returns: items, metadata.
- ...and 65 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
