io.github.vish288/mcp-argocd
Argo CD MCP server (MCP 2026-07-28): status, sync, rollback, drift, AppSets; writes or read-only
The current version, v0.5.3, was published to the official MCP registry on 2026-10-22. It is distributed as mcp-argocd on PyPI, filed under Kubernetes by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using io.github.vish288/mcp-argocd in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool provides Argo CD status, sync, rollback, drift, AppSets; read/write.”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-24).
Contracts can change after screening, with no version bump. The gate pins io.github.vish288/mcp-argocd’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for io.github.vish288/mcp-argocd](https://mcpindex.ai/server/io-github-vish288-mcp-argocd) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-vish288-mcp-argocd">Independent trust record for io.github.vish288/mcp-argocd</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-vish288-mcp-argocd)<a href="https://mcpindex.ai/server/io-github-vish288-mcp-argocd"><img src="https://mcpindex.ai/api/v1/badge/io-github-vish288-mcp-argocd" alt="mcpindex verdict" height="20" /></a>ARGOCD_TOKENArgo CD bearer token (also accepts ARGOCD_AUTH_TOKEN or ARGOCD_API_TOKEN)
ARGOCD_URLArgo CD base URL including any path prefix (e.g. https://argocd.example.com)
ARGOCD_READ_ONLYAlias for MCP_READ_ONLY. Any value other than false/0/no/off/empty locks the server read-only; --read-only can only raise the lock
MCP_READ_ONLYLocks the server read-only: write tools and write-workflow prompts are not listed and nothing lifts the lock at runtime. Shared name across the mcp-* servers; set it in the deployer's env
ARGOCD_HTTP_BEARER_TOKENBearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send it as 'Authorization: Bearer <token>'
List Civo instances, Kubernetes clusters, networks and DNS; reboot instances, add rules.
SDK for creating, managing, and operating Kubernetes clusters and workloads with ease.
VMware AVI (NSX ALB) load balancer plus AKO Kubernetes ops — 28 MCP tools.