Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 4
- 4 4
- 3 2
- 2 1
- 1 0
Trust in production
- Trust it - 45%
- With caveats - 55%
- Wouldn't - 0%
82% would recommend this server
How reviewers scored it
- Setup & docs 3.9
- Auth experience 4.0
- Reliability 3.9
- Maintainer responsiveness 3.7
Why it got a B
The Argo CD MCP server (Apache-2.0, TypeScript, npm argocd-mcp), first built at Akuity and now kept in the Argo project's argoproj-labs org. It talks to the Argo CD API with one API token you give it in an env var (or an HTTP header). Tools list clusters and applications, read resource trees, managed resources, events and workload logs, and create, update, sync and delete applications or run resource actions. MCP_READ_ONLY=true removes the five write tools. A token registry file lets one server reach several Argo CD instances without the token ever going to a host it wasn't meant for. In August 2026 a critical advisory showed 0.8.0's HTTP mode listening on every network interface with no password, so anyone who could reach it could deploy through your token; 0.9.0 fixed it the same day by binding to localhost and requiring MCP_AUTH_TOKEN for a wider bind. Biggest deduction: write tools are on by default and run with whatever your Argo CD token can do, so start with MCP_READ_ONLY=true and a token limited to the projects the AI should touch.
How to connect
// .cursor/mcp.json (README)
{ "mcpServers": { "argocd-mcp": { "command": "npx",
"args": ["argocd-mcp@latest", "stdio"],
"env": { "ARGOCD_BASE_URL": "<argocd_url>",
"ARGOCD_API_TOKEN": "<argocd_token>" } } } }
// .vscode/mcp.json (README)
{ "servers": { "argocd-mcp-stdio": { "type": "stdio",
"command": "npx", "args": ["argocd-mcp@latest", "stdio"],
"env": { "ARGOCD_BASE_URL": "<argocd_url>",
"ARGOCD_API_TOKEN": "<argocd_token>" } } } }
// claude_desktop_config.json (README)
{ "mcpServers": { "argocd-mcp": { "command": "npx",
"args": ["argocd-mcp@latest", "stdio"],
"env": { "ARGOCD_BASE_URL": "<argocd_url>",
"ARGOCD_API_TOKEN": "<argocd_token>" } } } }
Is Argo CD MCP Server (argocd-mcp) safe?
Is Argo CD MCP Server (argocd-mcp) safe to use?
Argo CD MCP Server (argocd-mcp) grades B (solid, with minor gaps). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. Updates are occasional, so fixes may be slow to arrive. It runs locally over stdio, so it acts with your machine's access.
Does Argo CD MCP Server (argocd-mcp) have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Argo CD MCP Server (argocd-mcp) support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Cloud & Hosting
- A AWS MCP ServerAWS's managed remote server for calling any AWS API, running sandboxed scripts, and searching AWS docs.
- A Cloudflare API MCP ServerOfficial hosted Cloudflare server that searches and calls the whole Cloudflare API (Workers, DNS, R2, D1, KV, firewall).
- A Netlify MCP ServerNetlify's official MCP server, hosted at mcp.netlify.com or run from npm, to create and deploy projects and manage env vars and secrets, forms, extensions and access controls.
- A Railway MCP (railway mcp in the Railway CLI)Railway's official MCP server, built into the Railway CLI and hosted at mcp.railway.com, to list projects and services, redeploy, and manage feature flags.
- A Render MCP ServerRender's official MCP server, hosted at mcp.render.com or run locally, to create services and databases, read logs and metrics, update environment variables and trigger deploys.
Community reviews
Set it up once, forgot about it
Of the Argo CD (argocd-) integrations I tried, this one is the most predictable. The Docker image made setup trivial and keeps it isolated. It is in our production agent and I sleep fine.
Used for Checking deploy status from chat
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Better than the DIY script it replaced
Clear tool names, sensible outputs, very few surprises. Release pace is moderate, so I pin a version and check in monthly. Auth is handled properly, and revoking access later was one click.
Used for Managing preview environments
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Solid core, fiddly setup
It does the job, but it took some tweaking. Auth is handled properly, and revoking access later was one click.
Used for Cost checks across projects
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Quietly reliable
Installed it on a Friday, it was part of my workflow by Monday. Auth is handled properly, and revoking access later was one click. Running it in Docker keeps it away from the rest of my machine. Happy to run it in production.
Used for Cost checks across projects
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Does the job, docs could be better
Good for experimenting, still deciding about production. Issues get answered eventually. Not fast, not abandoned. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Spinning up test resources
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
The Argo CD (argocd-) integration I wanted
Set this up for our team after comparing a few options. Sign-in flow was painless and I never had to paste a key into a config file. Good choice if you need Argo CD (argocd-) in your agent.
Used for Inventory of what is running where
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Easy win for our agent setup
Simple to set up in Cursor, simple to reason about. Updates are a bit slow, but it is stable enough that it has not mattered. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Fine in production if you sandbox it.
Used for Checking deploy status from chat
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Clean integration, sensible permissions
Been running this for about a month now. Scoped the token to just what the agent needs and it respected that.
Used for Reading logs during incidents
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Would not run this unattended
Setup was rough and the result was flaky. Sign-in flow was painless and I never had to paste a key into a config file. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. The Docker image made setup trivial and keeps it isolated. Keep permissions tight and it is a good tool.
Used for Inventory of what is running where
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Our team uses it every day
Our agents call this dozens of times a day. Used a fine-grained token with short expiry and it works fine with that. Scoped the token to just what the agent needs and it respected that. Recommended, with sensible guardrails.
Used for Reading logs during incidents
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Exactly what I needed from Argo CD (argocd-)
Tried it on a side project first, then rolled it out at work. Release pace is moderate, so I pin a version and check in monthly. Scoped the token to just what the agent needs and it respected that. Would recommend without hesitation.
Used for Spinning up test resources
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.