Argo CD MCP server
The Argo CD MCP server lets an agent inspect and manage GitOps applications — list and sync apps, read resource trees and workload logs, and run resource act...
The Argo CD MCP Server is an argoproj-labs implementation that connects an AI agent to your Argo CD instance so it can operate the GitOps control plane in natural language. The agent can list the clusters Argo CD manages, list and filter applications, and pull a detailed view of any single application including its sync and health status. From there it can act: trigger a sync to reconcile an app to the desired state in Git, create new applications, update existing ones, and delete them when needed.
For debugging a degraded deployment the server exposes the application resource tree, the managed resources, and the workload logs from the underlying pods and deployments, plus resource events — everything an agent needs to explain why an app is out of sync or unhealthy and propose a fix. It can also list the available resource actions for an object and run them. It runs over both stdio and an HTTP stream transport via npx, authenticating with your Argo CD server URL in ARGOCD_BASE_URL and an API token in ARGOCD_API_TOKEN. A read-only guard (MCP_READ_ONLY) lets you hand it a production instance for investigation without write risk, and NODE_TLS_REJECT_UNAUTHORIZED supports self-signed certificates.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Available tools
| Tool | Description |
|---|---|
| list_clusters | Lists all clusters registered with Argo CD. |
| list_applications | Lists and filters Argo CD applications. |
| get_application | Retrieves detailed information about a single application, including sync and health status. |
| create_application | Creates a new Argo CD application. |
| update_application | Modifies an existing application. |
| delete_application | Removes an application. |
| sync_application | Triggers a sync to reconcile an application to the desired state in Git. |
| get_application_resource_tree | Returns the resource hierarchy for an application. |
| get_application_managed_resources | Returns the resources managed by an application. |
| get_application_workload_logs | Retrieves logs from an application's pods and deployments. |
| get_resource_events | Lists events for a resource. |
| get_resource_actions | Lists the actions available for a resource. |
| run_resource_action | Executes an action against a resource. |
Required configuration
- ARGOCD_BASE_URLRequired
Base URL of your Argo CD instance (e.g. https://argocd.example.com).
- ARGOCD_API_TOKENRequired
Argo CD API token used to authenticate API calls.
- MCP_READ_ONLYOptional
Set to true to disable all write tools and run in investigation-only mode. Defaults to false.
- NODE_TLS_REJECT_UNAUTHORIZEDOptional
Set to 0 to allow self-signed Argo CD certificates. Defaults to enforcing TLS verification.
What you can do with it
Debug an out-of-sync application
Ask the agent why an app is degraded and it reads the resource tree, managed resources, events, and pod workload logs, then explains the drift and proposes the fix.
Sync a deployment from chat
Once a change lands in Git, the agent triggers a sync to reconcile the application to the desired state, closing the GitOps loop without you opening the Argo CD UI.
FAQ
- Is it free?
- Yes. mcp-for-argocd is open source under Apache-2.0 in the argoproj-labs organization and free to run; you only need an Argo CD instance and an API token scoped to what the agent should reach.
- Does it support remote/OAuth?
- It runs locally via npx over stdio or an HTTP stream transport, authenticating with ARGOCD_BASE_URL and an ARGOCD_API_TOKEN. There is no hosted OAuth endpoint; you point it at your own Argo CD server.
- Can I stop it from changing my applications?
- Yes. Set MCP_READ_ONLY to true to disable the create, update, delete, sync, and run-action tools so the agent can investigate a production instance without write access.