MCP Argocd MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-argocd -e 'ARGOCD_TOKEN=<ARGOCD_TOKEN>' -e 'ARGOCD_URL=<ARGOCD_URL>' -- uvx mcp-argocd

{
  "mcpServers": {
    "mcp-argocd": {
      "command": "uvx",
      "args": [
        "mcp-argocd"
      ],
      "env": {
        "ARGOCD_TOKEN": "<ARGOCD_TOKEN>",
        "ARGOCD_URL": "<ARGOCD_URL>"
      }
    }
  }
}

[mcp_servers.mcp-argocd]
command = "uvx"
args = ["mcp-argocd"]
env = { ARGOCD_TOKEN = "<ARGOCD_TOKEN>", ARGOCD_URL = "<ARGOCD_URL>" }

{
  "mcpServers": {
    "mcp-argocd": {
      "command": "uvx",
      "args": [
        "mcp-argocd"
      ],
      "env": {
        "ARGOCD_TOKEN": "<ARGOCD_TOKEN>",
        "ARGOCD_URL": "<ARGOCD_URL>"
      }
    }
  }
}

{
  "servers": {
    "mcp-argocd": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-argocd"
      ],
      "env": {
        "ARGOCD_TOKEN": "<ARGOCD_TOKEN>",
        "ARGOCD_URL": "<ARGOCD_URL>"
      }
    }
  }
}

Put your own values in place of <ARGOCD_TOKEN> (Argo CD bearer token (also accepts ARGOCD_AUTH_TOKEN or ARGOCD_API_TOKEN)), <ARGOCD_URL> (Argo CD base URL including any path prefix (e.g. https://argocd.example.com)). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: ARGOCD_READ_ONLY (Alias for MCP_READ_ONLY. Any value other than false/0/no/off/empty locks the server read-only; --read-only can only raise the lock), MCP_READ_ONLY (Locks the server read-only: write tools and write-workflow prompts are not listed and nothing lifts the lock at runtime. Shared name across the mcp-* servers; set it in the deployer's env), ARGOCD_HTTP_BEARER_TOKEN (Bearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send it as 'Authorization: Bearer <token>').