argocd

This MCP server exposes ArgoCD functionality as a set of tools accessible via the MCP protocol. It provides a suite of tool calls such as list_application, get_application, get_application_manifests, get_application_events, get_application_logs, get_application_resource_tree, create_application, sync_application, refresh_application, delete_application, and terminate_operation, as well as analogous operations for ApplicationSets, Projects, Clusters, and Repositories. Each tool is invoked through a tools/call RPC command with a name corresponding to the operation and a JSON arguments object detailing the inputs. For example, to list applications you would call the list tool with optional filters like project, cluster, namespace, or label selectors. The server uses ArgoCD under the hood to manage and retrieve state, deploy manifests, and interact with the Kubernetes cluster(s) configured in ArgoCD.

Prerequisites:

• Go 1.21+ (for building from source)
• Access to an ArgoCD server with an API token

Installation steps:

1. Install Go if not already installed.
2. Build the MCP server binary:

go build -o argocd-mcp-server ./cmd/argocd-mcp-server

3. Run the server locally (example):

./argocd-mcp-server

4. Alternatively, containerized usage (recommended for production):

# Build or pull the image and run it with appropriate environment variables
# Example using a prebuilt image
docker pull argocd-mcp-server:latest

Configure environment variables as described in the mcp_config section to connect to your ArgoCD instance.

Tips and common considerations:

• Ensure ARGOCD_AUTH_TOKEN and ARGOCD_SERVER point to a valid ArgoCD instance with network reachability from the MCP server.
• If your ArgoCD instance uses TLS with a self-signed certificate, set ARGOCD_INSECURE to true or configure proper CA certificates.
• Use LOG_LEVEL and LOG_FORMAT to control log verbosity and structure for easier troubleshooting.
• The MCP server communicates over stdin/stdout by default in the examples; when using a container, adapt the I/O as needed (e.g., via a gRPC bridge or a wrapper that translates to stdin/stdout).
• Review IAM and RBAC implications in ArgoCD to ensure the MCP server actions (create/sync/delete) have appropriate permissions.
• When using ApplicationSets, Projects, Clusters, or Repositories, provide precise inputs (names, namespaces, and repository URLs) to avoid ambiguous operations.