ArgoCD MCP Server
11 MCP tools for ArgoCD GitOps operations — applications, sync, rollback, projects, and repositories.
Overview
The ArgoCD MCP Server provides 11 tools for interacting with the platform’s ArgoCD instance, which manages GitOps-driven deployments across the Kubernetes clusters. Operators can query application status, trigger syncs, perform rollbacks, and inspect projects and repositories through Compass chat.
| Property |
Value |
| Port |
50051 |
| Transport |
JSON-RPC at /jsonrpc |
| Namespace |
f3iai |
Applications
| Tool |
Description |
argocd_list_applications |
List all ArgoCD applications with sync and health status |
argocd_get_application |
Get detailed application information including source, destination, sync status, and resource tree |
argocd_sync_application |
Trigger a sync for an application, optionally with prune or force flags |
argocd_rollback_application |
Rollback an application to a previous revision |
argocd_get_application_resources |
List all Kubernetes resources managed by an application |
argocd_get_application_events |
Get recent events for an application (sync, health transitions, errors) |
argocd_get_application_logs |
Get logs from pods managed by an application |
Projects
| Tool |
Description |
argocd_list_projects |
List all ArgoCD projects |
argocd_get_project |
Get project details including source/destination restrictions and roles |
Repositories
| Tool |
Description |
argocd_list_repositories |
List all configured Git repositories |
argocd_get_repository |
Get details of a specific repository including connection status |
Common Use Cases
- “What apps are out of sync?” — calls
argocd_list_applications and filters by sync status
- “Sync the compass-api app” — calls
argocd_sync_application
- “Rollback ffo-mcp to the previous version” — calls
argocd_rollback_application
- “Show me the resources in the ffp-ffo-mcp app” — calls
argocd_get_application_resources
- “What repos are configured?” — calls
argocd_list_repositories
- “Why is compass-api degraded?” — calls
argocd_get_application_events for recent errors
Authentication
The server authenticates to ArgoCD using an API token:
| Environment Variable |
Description |
ARGOCD_URL |
ArgoCD server URL |
ARGOCD_TOKEN |
API token with read/write access |
ARGOCD_INSECURE |
Skip TLS verification (default: true for in-cluster) |
Health Endpoints
| Endpoint |
Purpose |
/health |
Liveness — process is running |
/ready |
Readiness — can authenticate to ArgoCD API |