For Argocd MCP Server
Argo CD applications and clusters managed through natural language AI assistant interfaces.
Data last scanned today · Reviewed today
Overview
This server bridges Argo CD with AI assistants, allowing users to query and interact with their application deployments using natural language. It is designed to function as an MCP server, providing standard tool definitions that enable AI clients to fetch resource details or list infrastructure components directly from an Argo CD instance. The tool facilitates integration via stdio and HTTP stream transport protocols, making it compatible with various development environments, including Visual Studio Code. It offers specific capabilities for cluster listing, project information retrieval, and application management, streamlining interaction with Argo CD resources during development workflows.
Our verdict
This server carries a high-risk profile with a security score of 48/100. The primary concerns stem from the lack of review regarding read-only mode, OAuth, and authentication mechanisms, which are critical for an tool interacting with CI/CD infrastructure. While the project is active and benefits from a decent contributor base, it is community-maintained and not officially supported by the Argo project, so users should exercise caution before deploying it in sensitive environments.
- Supports stdio and HTTP stream transport protocols
- Small supply-chain footprint with only 6 direct dependencies
- Active development with a recent commit 18 days ago
- Broad community backing with 547 GitHub stars
- Read-only and OAuth support have not been reviewed
- Authentication mechanisms remain unverified
- Community-maintained without official Argo project backing
Setup
{
"mcpServers": {
"mcp-for-argocd": {
"args": [
"-y",
"argocd-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| list_clusters | List all clusters registered with ArgoCD | low |
| get_appproject | Get detailed information about a specific AppProject (project) | low |
| list_applications | List and filter all applications | low |
| get_application | Get detailed information about a specific application | low |
| create_application | Create a new application | medium |
| update_application | Update an existing application | medium |
| delete_application | Delete an application | high |
| sync_application | Trigger a sync operation on an application | medium |
| get_application_resource_tree | Get the resource tree for a specific application | low |
| get_application_managed_resources | Get managed resources for a specific application | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What prerequisites are required to run this MCP server?
You need Node.js version 18 or higher, access to an Argo CD instance, and an Argo CD API token.
›Which transport protocols are supported?
The server supports both stdio and HTTP stream transport modes for integration with various MCP clients.
›How do I handle self-signed certificates in my Argo CD environment?
You can add the environment variable NODE_TLS_REJECT_UNAUTHORIZED set to 0 in your server configuration.
›What environment variables are necessary for the server to function?
The server requires the ARGOCD_BASE_URL and ARGOCD_API_TOKEN environment variables to be configured.
Changelog
Badge
Maintain this server? Add the live badge to your README.