Argo CD MCP Server

Community

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

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #14 of 438
Stars: ★ 585 Very popular
Transport: stdio (local process) · Streamable HTTP
Runtime: Node.js 18+
Credentials: API key / credential required
License: Apache-2.0
Last commit: 2 months ago
Tools: 14

71FMRS · B

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.

Strongest · Maintenance 16/20 Weakest · Reliability 10/20

Reliability

10/20

Security and permissions

16/20

Maintenance

16/20

Documentation

15/20

Setup experience

14/20

Why each score

Reliability 10/20: Although the README provides extensive tool and configuration documentation, this static review found no evidence of executable tests or CI workflows. The only workflow is a release GitHub Action that doesn't exercise key paths. Hence, reliability is capped at 10 due to lack of verifiable execution evidence.
Security and permissions 16/20: The server shows good security practices: token binding to default base URL, token registry for multi-instance, read-only mode enforced, tokens never passed as tool arguments, and fail-closed startup on registry misconfiguration. However, there's no evidence of explicit interactive confirmation for dangerous operations or audit logging, so deductions apply.
Maintenance 16/20: The repository is actively maintained under argoproj-labs, has Apache-2.0 license, recent commits, and an active release workflow. Issue responsiveness cannot be verified. No security vulnerability reporting channel is disclosed. Thus, deductions apply for issue response and vulnerability disclosure.
Documentation 15/20: The README is quite comprehensive covering installation, configuration, token resolution, multi-instance support, read-only mode, stateless mode, and local development. Missing end-user troubleshooting guide and per-tool parameter details (though types exist) is a minor shortfall.
Setup experience 14/20: Clear installation steps for multiple clients (Cursor, VS Code, Claude Desktop), with support for stdio and HTTP transports. Depends on npx and Node 18+, and requires an API token. Score lowered due to lack of executed end-to-end verification; documented steps align with standard practices.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

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.

Setup

Before you start

Runtime：Node.js 18+

ARGOCD_API_TOKEN requiredsecret Argo CD API token (required), generated per the Argo CD authorization docs.

MCP_AUTH_TOKEN optionalsecret Inbound auth token; when set, all HTTP requests must carry a Bearer token.

Other optional settings (5)

ARGOCD_BASE_URL optional Base URL of your Argo CD instance's API, from your Argo CD deployment.

NODE_TLS_REJECT_UNAUTHORIZED optional Set to "0" to skip TLS validation for self-signed certificates; dev use only.

ARGOCD_TOKEN_REGISTRY_PATH optional Path to a JSON token registry file mapping base URLs to tokens for multi-instance setups.

MCP_READ_ONLY optional Set to "true" to enable read-only mode, disabling create/update/delete/sync tools.

MCP_BIND_ADDRESS optional HTTP bind address, defaults to 127.0.0.1.

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>"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add argocd-mcp -e 'ARGOCD_BASE_URL=<argocd_url>' -e 'ARGOCD_API_TOKEN=<argocd_token>' -- npx argocd-mcp@latest stdio

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

The argocd-mcp tools (e.g. list_clusters, list_applications) should appear in your client's tool list; calling list_applications and getting your Argo CD applications back confirms the connection works.

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`.

Things to try

Once connected, you can ask your AI assistant things like:

List all clusters registered with Argo CD
Show detailed information for the guestbook application
Trigger a sync for my application
Get the workload logs for my-app

Tools 14

list_clusters read-only

List all clusters registered with ArgoCD.

get_appproject read-only

Get detailed information about a specific AppProject (project).

list_applications read-only

List and filter all applications.

get_application read-only

Get detailed information about a specific application.

create_application writes

Create a new application.

update_application writes

Update an existing application.

delete_application destructive

Delete an application.

sync_application writes

Trigger a sync operation on an application.

Show 6 more tools

get_application_resource_tree read-only

Get the resource tree for a specific application.

get_application_managed_resources read-only

Get managed resources for a specific application.

get_application_workload_logs read-only

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

get_resource_events read-only

Get events for resources managed by an application.

get_resource_actions read-only

Get available actions for resources.

run_resource_action writes

Run an action on a resource.

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 Desktop

VS Code

Cursor

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 410 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.5k · Tools 15 Compare with this →

Compare with other MCP servers

Source revision 28d15ca69b0c Data synced 2026-10-12 Read the FMRS scoring method