MCP SERVERFind out why an Argo CD application is degraded — resource tree, events, container logs — and sync, prune or roll a change from the same session.
LABSCO SUMMARY
Diagnosis and remedy sit in one server: you can walk from application to resource tree to the failing pod's container logs, then sync with prune and a pinned revision in the next call. The filtering on managed resources is the tell that this was built against real clusters — a large application returns more than a model can hold, and kind, namespace and project narrow it before that becomes a problem.
An Argo CD API client covering the read path an operator uses during an incident and the write path that resolves it. It speaks stdio for a local client and HTTP stream for a shared deployment, against the instance named by its base URL — or several instances, when you give it a token registry.
An Argo CD instance reachable at ARGOCD_BASE_URL and an API token in ARGOCD_API_TOKEN. The token's rights decide what succeeds, and applications in non-default namespaces need their namespace named or the call fails on permissions. For several instances, point ARGOCD_TOKEN_REGISTRY_PATH at a JSON file — a mounted secret, say — keyed by base URL; the default token is bound to the default instance and is never sent to another host, so an override without a registry entry fails before any request goes out. A registry path that is missing or malformed stops the server at startup rather than quietly using the wrong credential.
One command plus a key — docker run -e ARGOCD_BASE_URL=<YOUR_ARGOCD_BASE_URL> -e ARGOCD_API_TOKEN=<YOUR_ARGOCD_API_TOKEN> argoprojlabs/mcp-for-argocd
USE CASES
Read the application, walk its resource tree to the unhealthy resource, then read that resource's events.
Pull logs from the workload, narrowed to the container that is actually failing.
Dry-run the sync first, then sync for real with prune and the revision you mean.
Fetch the live manifests for the resources in question rather than reading the Git side and assuming.
Read the AppProject the application belongs to — the destinations and sources it permits are in there.
Create it in the namespace you want, then update and sync it once the first attempt shows what was missing.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_applicationcreate_application creates a new ArgoCD application in the specified namespace. The application.metadata.namespace field determines where the Application resource will be created (e.g., "argocd", "argocd-apps", or any custom namespace).
delete_applicationdelete_application deletes application. Specify applicationNamespace if the application is in a non-default namespace to avoid permission errors.
get_applicationget_application returns application by application name. Optionally specify the application namespace to get applications from non-default namespaces.
get_application_eventsget_application_events returns events for application by application name. Optionally specify the application namespace to get events from applications in non-default namespaces.
get_application_managed_resourcesget_application_managed_resources returns managed resources for application by application name with optional filtering. Use filters to avoid token limits with large applications. Examples: kind="ConfigMap" for config maps only, namespace="production" for specific namespace, or combine multiple filters.
get_application_resource_treeget_application_resource_tree returns resource tree for application by application name. Optionally specify the application namespace to get resource tree from applications in non-default namespaces.
get_application_workload_logsget_application_workload_logs returns logs for application workload (Deployment, StatefulSet, Pod, etc.) by application name and resource ref and optionally container name
get_appprojectget_appproject returns an ArgoCD AppProject (project) by its name. AppProjects provide a logical grouping of applications and define allowed sources, destinations, cluster/repository whitelists, and RBAC roles.
get_resource_actionsget_resource_actions returns actions for a resource that is managed by an application
get_resource_eventsget_resource_events returns events for a resource that is managed by an application
get_resourcesget_resources return manifests for resources specified by resourceRefs. If resourceRefs is empty or not provided, fetches all resources managed by the application.
list_applicationslist_applications returns list of applications
list_clusterslist_clusters returns list of clusters registered with ArgoCD
run_resource_actionrun_resource_action runs an action on a resource
sync_applicationsync_application syncs application. Specify applicationNamespace if the application is in a non-default namespace to avoid permission errors.
update_applicationupdate_application updates application
BEFORE YOU INSTALL
16 tools when we connected. The documentation lists 14, leaving out get_application_events and get_resources. MCP_READ_ONLY=true removes create_application, update_application, delete_application, sync_application and run_resource_action, leaving 11.
All 3 documented clients run the server on your machine.
CONTEXT COST
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
docker run -e ARGOCD_BASE_URL=<YOUR_ARGOCD_BASE_URL> -e ARGOCD_API_TOKEN=<YOUR_ARGOCD_API_TOKEN> argoprojlabs/mcp-for-argocd{
"mcpServers": {
"argocd-mcp": {
"command": "npx",
"args": [
"argocd-mcp@latest",
"stdio"
],
"env": {
"ARGOCD_BASE_URL": "<YOUR_ARGOCD_BASE_URL>",
"ARGOCD_API_TOKEN": "<YOUR_ARGOCD_API_TOKEN>"
}
}
}
}{
"servers": {
"argocd-mcp-stdio": {
"type": "stdio",
"command": "npx",
"args": [
"argocd-mcp@latest",
"stdio"
],
"env": {
"ARGOCD_BASE_URL": "<YOUR_ARGOCD_BASE_URL>",
"ARGOCD_API_TOKEN": "<YOUR_ARGOCD_API_TOKEN>"
}
}
}
}MCP servers
rohitg00
StacklokLabs
AkibaAT
ckreiling