# Argocd [Health: Active]

**Category:** 🔒 Delivery  
**Repository:** https://github.com/asklokesh/argocd-mcp-server  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/argocd

## Description
MCP server for ArgoCD GitOps continuous delivery integration

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "argocd": {
    "command": "uvx",
    "args": ["argocd-mcp-server"],
    "env": {
      "ARGOCD_SERVER": "",
      "ARGOCD_AUTH_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `ARGOCD_SERVER`, `ARGOCD_AUTH_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Argocd MCP server does

Argocd MCP server connects MCP-compatible AI applications with ArgoCD, the GitOps continuous delivery system. It is intended for managing Kubernetes deployments through ArgoCD APIs rather than operating on Kubernetes resources directly. The documented scope includes application lifecycle operations, project configuration, repository and Helm source management, cluster registration, synchronization, rollback, and deployment health inspection.

The server also describes support for multi-cluster setups and ApplicationSets. These features can help an agent work with several ArgoCD instances or create template-based deployments across clusters. The README additionally lists sync windows, hooks, RBAC-related operations, JWT tokens, automated rollback, progressive delivery, audit logging, and secret-management integration as supported areas.

## How it works

The process runs as a Python MCP server and reads ArgoCD connection details from environment variables. A primary instance is configured with `ARGOCD_SERVER` and `ARGOCD_AUTH_TOKEN`; optional settings control insecure connections, gRPC-Web usage, request timeout, and client certificates. Separate server and token variables can be supplied for production and development instances.

An MCP client invokes named operations such as application listing, application creation, synchronization, status checks, and rollback. Requests can include ArgoCD concepts such as projects, repositories, destinations, revisions, pruning, force behavior, and sync strategies. Health tools return application health or a resource tree for inspection.

## Setup and configuration

Install the published Python package with:

```bash
pip install argocd-mcp-server
```

The project can also be installed from a cloned source checkout with editable installation. Configuration may be placed in a `.env` file or exported in the process environment. The documented connection settings are:

```env
ARGOCD_SERVER=argocd.example.com
ARGOCD_AUTH_TOKEN=your_auth_token
ARGOCD_INSECURE=false
```

Optional variables include `ARGOCD_GRPC_WEB`, `ARGOCD_TIMEOUT`, `ARGOCD_CLIENT_CERT`, and `ARGOCD_CLIENT_KEY`. For Claude Desktop, the README uses `python -m argocd_mcp.server` as the command and passes the ArgoCD server and token through the client configuration.

## Tools and capabilities

Argocd MCP server documents tools for:

- Listing, creating, syncing, deleting, and rolling back applications
- Reading application status, health, and resource trees
- Creating and configuring ArgoCD projects
- Adding Git and Helm repositories
- Registering Kubernetes clusters
- Creating ApplicationSets for templated multi-cluster deployments
- Managing sync policies, hooks, and related deployment behavior
- Supporting project roles, policies, users, and JWT tokens

The examples show automated sync with pruning and self-healing, repository credentials, cluster bearer tokens, and ApplicationSet generators based on cluster labels.

## Limitations and notes

The server requires access to an ArgoCD instance and valid authentication material. The README lists JWT or API token authentication and mentions OIDC/OAuth2 and LDAP support, but it does not provide configuration examples for every authentication method. Multi-cluster configuration is documented through separate server and token values, with a selectable default cluster.

The supplied material does not identify a license name, supported ArgoCD version, or a complete tool inventory beyond the examples and feature categories shown. Treat those details as items to verify before production deployment.

_Full upstream README: https://allmcps.com/mcp/argocd/readme_