← Back to directory

Argo CD MCP Server

Community

An MCP server for Argo CD, enabling AI assistants to interact with your Argo CD applications through natural language.

GitHub source repository ↗

★ 559 Stars Category · Dev Tools Very popular Source revision 28d15ca69b0c

71FMRS · B

Reliability

10/20

Security and permissions

16/20

Maintenance

16/20

Documentation

15/20

Setup experience

14/20

This project is maintained by the Argo community and offers a rich set of Argo CD management tools with multi-transport and read-only mode. Security design is solid, but attention is needed for token management and write operation risks.

Read the FMRS scoring method →

The Argo CD MCP Server is an implementation of the Model Context Protocol (MCP) for Argo CD. It allows AI assistants to interact with Argo CD applications seamlessly, supporting stdio and HTTP stream transports for integration with Visual Studio Code and other MCP clients. It provides comprehensive tools for managing clusters, projects, applications, and resources, including sync, logs, and events.

Tools

list_clusters

List all clusters registered with ArgoCD.

get_appproject

Get detailed information about a specific AppProject (project).

list_applications

List and filter all applications.

get_application

Get detailed information about a specific application.

create_application

Create a new application.

update_application

Update an existing application.

delete_application

Delete an application.

sync_application

Trigger a sync operation on an application.

get_application_resource_tree

Get the resource tree for a specific application.

get_application_managed_resources

Get managed resources for a specific application.

get_application_workload_logs

Get logs for application workloads (Pods, Deployments, etc.).

get_resource_events

Get events for resources managed by an application.

get_resource_actions

Get available actions for resources.

run_resource_action

Run an action on a resource.

Setup

Prerequisites: Node.js (v18+ recommended), an Argo CD instance with API access, and an API token (see Argo CD docs).
Configure your MCP client (e.g., Claude Desktop, VS Code, Cursor) with the server configuration: command npx, args argocd-mcp@latest stdio, env ARGOCD_BASE_URL and ARGOCD_API_TOKEN.
For Cursor: create .cursor/mcp.json in your project.
For VS Code: create .vscode/mcp.json.
For Claude Desktop: edit claude_desktop_config.json.
If using self-signed certificates, set NODE_TLS_REJECT_UNAUTHORIZED=0.

claude_desktop_config.json

{
  "mcpServers": {
    "argocd-mcp": {
      "command": "npx",
      "args": ["argocd-mcp@latest", "stdio"],
      "env": {
        "ARGOCD_BASE_URL": "<argocd_url>",
        "ARGOCD_API_TOKEN": "<argocd_token>"
      }
    }
  }
}

Generate and validate client config

Fit and risk

Best for

DevOps teams wanting to use AI assistants with Argo CD.
Users with GitOps workflows needing natural language management of Kubernetes applications.
Developers using MCP within VS Code or Cursor.

Not for

Production environments with strict security boundaries that cannot expose API tokens to AI assistants.
Multi-replica deployments without sticky sessions unless running `--stateless` mode.

Required permissions

Requires access to the Argo CD API, including read permissions for clusters, applications, resource trees, logs, events, etc.
Write operations (create, update, delete, sync, run action) require appropriate Argo CD RBAC permissions.
The server reads API tokens from environment variables or HTTP headers, never exposing them in tool calls.

Risks and side effects

API tokens are sensitive; must be stored securely and not leaked.
Write operations can modify or delete applications; use with caution.
Disabling TLS verification for self-signed certificates reduces security.
Default token is bound to the default base URL to prevent credential exfiltration, but misconfiguration can cause fail-closed behavior.

Troubleshooting

Check that `ARGOCD_BASE_URL` and `ARGOCD_API_TOKEN` are set correctly.
Verify that the Argo CD API is reachable from the server's network.
If authentication fails, check that the token is valid and has required permissions.
For multiple instances, ensure `ARGOCD_TOKEN_REGISTRY_PATH` points to a valid JSON file.
If using self-signed certificates, set `NODE_TLS_REJECT_UNAUTHORIZED=0`.

Use cases

Query application status and resource configurations in Argo CD using natural language.

Create, update, or delete Argo CD applications via an AI assistant.

Trigger application syncs to deploy latest changes.

Fetch workload logs and resource events for troubleshooting.

Target multiple Argo CD instances using base URL overrides with token registry.

Supported clients

Claude DesktopFull support

Visual Studio CodeFull support

CursorFull support

Related MCP servers

Compare with other MCP servers