Argo CD MCP Server
An MCP server for Argo CD: applications, resource trees, logs, events, sync and resource actions
- 599 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Can delete and sync applications in clusters
- Uses an Argo CD API token
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/argo-cd-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can delete and sync applications in clusters
- Uses an Argo CD API token
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 wrongMCP
- Transport
- stdio, http, sse
- Authentication
- API key
Environment variables
ARGOCD_BASE_URLrequired- Default Argo CD instance URL.
ARGOCD_API_TOKENrequired, 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_TOKENsecret- Inbound Bearer token for HTTP mode.
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
MCP serversA secure MCP runtime through which an agent operates local machines, servers and containers
Self-hosted MCP server for running commands on remote servers over SSH, with tokens and roles
Azure DevOps MCP server
Azure DevOps MCP Server
Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Microsoft's official MCP server for Azure: the agent sees subscription resources and works with Azure services on your behalf
Datadog's official managed MCP server: logs, metrics, traces and incidents right in your agent
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.