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 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
- AlicenseAqualityBmaintenanceSafety-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
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose deployments, releases, runbooks, tasks, tenants, and infrastructure inside an Octopus instance through its APIs. Supports read-only and write-gated modes, toolset selection, and structured REST access for both interactive use and automation.402 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to connect to an Octopus instance to inspect, query, and diagnose deployment problems, with toolsets covering projects, releases, deployments, runbooks, tenants, Kubernetes, machines, and accounts. Supports read-only mode and gated write operations for creating releases, deploying, and running runbooks.402 npmMIT
TDQS
Scored across 37 tools
Most tools have a clearly distinct resource+action target, and the read-heavy application tools (get_application, get_resource_tree, get_managed_resources, get_resource, get_manifests) are separated by descriptions explaining live vs desired vs single-resource scope. The only mild risk is confusion between the managed-resource/rendered-manifest readers and between list_applicationsets/get_applicationset, but the wording disambiguates them adequately.
Every tool follows the same argocd_verb_noun snake_case pattern (argocd_list_applications, argocd_get_application, argocd_patch_application, argocd_delete_resource). Exceptions like argocd_can_i and argocd_get_version still fit the prefix+verb convention, so the surface is highly predictable.
37 tools is heavy and above the comfortable band, but Argo CD is a genuinely broad domain (clusters, repos, projects, ApplicationSets, applications, resources, logs, operations) and most tools map to a distinct operation rather than duplicating each other. A few informational tools (get_version, get_settings, get_userinfo, can_i) could plausibly be consolidated, so it sits at the borderline rather than being well-scoped.
Application lifecycle is well covered (list/get/create/patch/delete plus sync, rollback, terminate, history, logs, events), and per-resource actions and deletion exist. However, there is no create/update/delete for projects, clusters, repositories, or ApplicationSets (generate_applicationset is dry-run only), leaving notable management gaps for a server whose stated scope spans those entities.