Argo CD MCP Server

Name: Argo CD MCP Server
Author: akuity

@akuity

Repository Homepage

About Argo CD MCP Server

An implementation of Model Context Protocol (MCP) server for Argo CD.

#argocd #kubernetes #devops

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Argo CD MCP Server?

An implementation of the Model Context Protocol (MCP) server for Argo CD, enabling AI assistants to interact with Argo CD applications through natural language. It integrates with Visual Studio Code, Cursor, Claude Desktop, and other MCP clients via stdio and HTTP stream transport protocols.

How to use Argo CD MCP Server?

Set the ARGOCD_BASE_URL and ARGOCD_API_TOKEN environment variables, then run npx argocd-mcp@latest stdio. Create an MCP configuration file (e.g., .cursor/mcp.json, .vscode/mcp.json, or claude_desktop_config.json) with the command and env values to integrate with supported clients.

Key features of Argo CD MCP Server

Supports stdio and HTTP stream transport protocols
Comprehensive access to Argo CD resources and operations (clusters, applications, logs, events)
Pre-configured tools for AI assistants to interact with Argo CD in natural language
Token registry for securely targeting multiple Argo CD instances with per-host tokens
Support for self-signed certificates via the NODE_TLS_REJECT_UNAUTHORIZED environment variable

Use cases of Argo CD MCP Server

List and filter all Argo CD applications from an AI assistant
Trigger a sync operation on an application after a code change
Retrieve resource trees, managed resources, and workload logs for troubleshooting
Get events and available actions for resources and execute actions
Manage multiple Argo CD instances from a single MCP server using a token registry

FAQ from Argo CD MCP Server

What are the prerequisites for using Argo CD MCP Server?

Node.js v18 or higher (for running npx), an Argo CD instance with API access, and an Argo CD API token.

How do I provide Argo CD credentials?

The base URL is supplied via the ARGOCD_BASE_URL environment variable (or x-argocd-base-url HTTP header) and optionally overridden per tool call with the argocdBaseUrl argument. The API token is mandatory and read from the ARGOCD_API_TOKEN environment variable (or x-argocd-api-token header for HTTP transport); it is never accepted as a tool argument to avoid leaking into prompts, model context, or logs.

How can I connect to multiple Argo CD instances with different tokens?

Set the ARGOCD_TOKEN_REGISTRY_PATH environment variable to point to a JSON file mapping base URLs to their tokens. The server then resolves the correct token per call, preventing token exfiltration by binding the default token only to the default base URL.

Can I use self-signed certificates with this server?

Yes. Set the NODE_TLS_REJECT_UNAUTHORIZED environment variable to "0" to disable TLS certificate validation. Use this only in development or when you understand the security implications.