Argocd MCP Server

Cluster and application listings provide a starting point for Argo CD troubleshooting. From there, an assistant can retrieve application details, inspect an AppProject's source and destination policies and roles, or examine the application's resource tree. Managed-resource queries accept filters such as kind and namespace, while manifest retrieval can cover selected resources or all resources managed by an application. Workload logs support resource and optional container selection, and separate event tools cover applications and individual resources. Namespace arguments also support several operations on applications outside the default namespace.

Application changes use dedicated tools for creation, updates, deletion, and synchronization; resource actions can be listed before execution. Read-only mode leaves inspection tools available but disables application changes, sync, and resource-action execution. Clients can connect over stdio or HTTP streaming, with configuration examples for Cursor, Visual Studio Code, and Claude Desktop. For multiple Argo CD instances, a file-based token registry associates credentials with base URLs. Tools can select an instance through a per-call base URL without taking API tokens as arguments. The default token remains tied to the default instance, while other instances need registry entries.