@godrix/argocd-mcp
Related Servers
Alternatives to @godrix/argocd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA secure MCP server providing read-only access to Argo CD instances using browser session cookies, enabling querying of applications, projects, clusters, and repositories.14MIT

argocd-mcpofficial
AlicenseCqualityCmaintenanceAn implementation of Model Context Protocol (MCP) server for Argo CD.1417,824 npm570Apache 2.0- 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 gradedqualityCmaintenanceA universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.Academic Free v1.1
- AlicenseNot gradedqualityAmaintenanceEnables 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
- FlicenseNot gradedqualityCmaintenanceMCP server to dispatch Argo WorkflowTemplates according to pipeline configurations, supporting multiple pipelines, authentication, and remote access.1-
TDQS
Scored across 26 tools
Most tools map to clearly distinct resources and actions, such as get-application, sync-application, and list-projects. A few pairs like view-application-observability vs diagnose-application or list-applications vs search-applications could be confused, but the descriptions provide enough distinction.
The majority of tools follow a readable verb-noun kebab-case pattern like get-application and sync-application. However, several tools use snake_case (argocd_login, argocd_set_api_key, argocd_auth_status) and a few use noun-first names like application-cache-status, making the overall naming style inconsistent.
With 26 tools, the server exceeds the 25-tool threshold and feels heavier than necessary. Several narrow helpers such as application-cache-status, refresh-application-cache, and observability-specific tools could be consolidated without losing core functionality.
The tool set covers Argo CD inspection, sync, refresh, auth, project listing, and troubleshooting well. However, there are notable lifecycle gaps: no create/update/delete application or project operations, and call-argocd-api is restricted to read-only GET calls.