mcp-argocd
Related Servers
Alternatives to mcp-argocd
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with ArgoCD APIs through standardized MCP tools for managing applications, resources, and deployments.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityAmaintenanceSafety-first GitOps operations for ArgoCD via the Model Context Protocol. Enables listing, diagnosing, syncing, and managing ArgoCD applications with progressive disclosure and defense-in-depth security.15Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to explore and operate OpenShift/Kubernetes clusters, offering read-only tools for projects, pods, logs, and resources, with opt-in higher modes for scaling, restarts, applying manifests, and deletions under safe-by-default guards.675 npmMIT
- AlicenseAqualityAmaintenanceEnables LLMs to search Flux HelmReleases and Argo Applications from kubesearch.dev, and temporarily clone repos to review actual manifests.118MIT
TDQS
Scored across 37 tools
Each tool targets a distinct Argo CD resource or action, such as applications, ApplicationSets, projects, clusters, repositories, and resource actions. Although there are many get_* tools, their scopes (tree, managed resources, single resource, manifests, events, logs) are clearly differentiated in the descriptions, so an agent can select correctly.
All tools use the argocd_ prefix and snake_case with consistent verb_noun or verb_noun_phrase patterns (e.g., argocd_list_applications, argocd_get_application, argocd_sync_application). Minor variations like argocd_can_i and argocd_get_userinfo are still predictable and readable.
37 tools far exceeds the typical 3-15 range and the rubric's threshold for 'too many' (25+). While Argo CD is a broad system, many tools could be consolidated (e.g., multiple resource-inspection tools) to reduce cognitive load.
The application lifecycle is well-covered (create, get, list, patch, delete, sync, rollback, terminate, wait, events, logs, history). However, other core Argo CD resources—ApplicationSets, Projects, Clusters, and Repositories—lack create/update/delete operations, leaving significant gaps that would cause agent failures when managing these resources.