ArgoCD MCP Server
Related Servers
Alternatives to ArgoCD MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to interact with Argo CD through its REST API, providing tools to triage application status, sync, roll back, inspect drift, read logs, and manage ApplicationSets, clusters, projects, and repositories. Supports read-only safeguards, curated GitOps resources, and workflow prompts for safe operations.3779 PyPIMIT
- AlicenseAqualityDmaintenanceAn MCP (Model Context Protocol) server that integrates with the ArgoCD API, enabling AI assistants and large language models to manage ArgoCD applications and resources through natural language interactions.1012MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to inspect Argo CD applications, check sync and health status, list resources, review events, refresh applications, and optionally trigger sync operations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with ArgoCD APIs through standardized MCP tools for managing applications, resources, and deployments.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.Apache 2.0
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action combination. Get/status/diff/history/logs/diagnose all serve clearly separate purposes. Sync and delete operations are cleanly separated from their non-prune vs prune variants, and the destructive tools include explicit confirmation requirements that distinguish them from safe operations.
The vast majority follow a consistent verb_noun pattern (get_application, list_applications, sync_application, delete_application, rollback_application). Minor deviation: diagnose_sync_failure, refresh_application, and terminate_sync don't carry the 'application' noun prefix, though this is readable and doesn't cause confusion.
Fifteen tools is well within the sweet spot for an operations-focused MCP server. Each tool covers a distinct lifecycle operation—read, list, sync, rollback, delete, diagnose, log retrieval, cluster/project listing—so every tool earns its place without redundancy.
The tool surface covers the full application lifecycle well: create/read/update/delete is mostly covered (notably missing application creation/update), plus sync, rollback, refresh, logs, diff preview, history, and failure diagnosis. No audit/events tool is missing; the only notable gap is application creation/update operations, plus cluster/project management is read-only.