Argo CD MCP Server
An MCP server for Argo CD: applications, resource trees, logs, events, sync and resource actions
Install
{
"mcpServers": {
"argocd-mcp": {
"command": "npx",
"args": [
"argocd-mcp@latest",
"stdio"
],
"env": {
"ARGOCD_BASE_URL": "<argocd_url>",
"ARGOCD_API_TOKEN": "<argocd_token>"
}
}
}
}For Cursor and Claude Desktop. Add "MCP_READ_ONLY": "true" to block changes.
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to Argo CD through its API. The agent sees clusters and projects, finds applications and inspects their status, resource tree, managed resources, workload logs and events. It can create, update, delete and sync applications and run available resource actions. Read-only mode limits tools to inspection, and a token registry supports several Argo CD instances.
Who it is for. For DevOps engineers running GitOps deployments on Argo CD.
Good fit when
- You need to find out why an application is OutOfSync or Degraded
- You need an application's logs and events without opening the UI
- You need to trigger a sync after changing manifests
Not a fit when
- You do not deploy with Argo CD
- The agent must not sync or delete and read-only mode is not enough
Example request
Show Argo CD applications in Degraded status and use events and logs to explain what is wrongLimitations
Requires the Argo CD URL and an API token; the agent gets the token's permissions. MCP_READ_ONLY=true leaves read access only. HTTP mode binds to localhost by default and needs MCP_AUTH_TOKEN to be exposed. For self-signed certificates the README suggests disabling TLS verification, which weakens security.
How to disable. Remove the argocd-mcp block from the MCP config and revoke the API token in Argo CD.
MCP
- Transport
- stdio, http, sse
- Authentication
- API key
| Environment variables | |
|---|---|
| ARGOCD_BASE_URL required | Default Argo CD instance URL. |
| ARGOCD_API_TOKEN required, secret | Argo CD API token, required unless a token registry is used. |
| MCP_READ_ONLY | true leaves read-only tools only. |
| ARGOCD_TOKEN_REGISTRY_PATH | Path to a JSON token registry for multiple instances. |
| MCP_AUTH_TOKEN secret | Inbound Bearer token for HTTP mode. |
Security check
- Can delete and sync applications in clusters
- Uses an Argo CD API token
README in short
The README lists tools for clusters, projects, applications and resources and gives npx configs for Cursor, VS Code and Claude Desktop. It details the token model: tokens never appear in tool arguments, and other instances use a registry. Separate sections cover HTTP network exposure, read-only mode, stateless mode and Docker. The project was started at Akuity and donated to argoproj-labs. Apache-2.0 licensed.
FAQ
How do I stop the agent from changing applications?
Set MCP_READ_ONLY=true to disable create, delete, sync and resource actions.
Can it work with several Argo CD instances?
Yes, via a JSON token registry file in ARGOCD_TOKEN_REGISTRY_PATH. The agent passes only the URL and the server attaches the token.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes