Argocd MCP Server

Argocd mcp mcp server connects Argocd MCP to AI assistants that speak the Model Context Protocol. An MCP (Model Context Protocol) server that integrates with the ArgoCD API, enabling AI assistants and large language models to manage ArgoCD applications and resources through natural language interactions.

What Argocd MCP does

An MCP (Model Context Protocol) server that integrates with the ArgoCD API, enabling AI assistants and large language models to manage ArgoCD applications and resources through natural language interactions.

Key capabilities

• Authentication & Session Management —
• User info retrieval from ArgoCD API
• Token-based authentication with ArgoCD
• Server settings and configuration access
• Plugin information retrieval
• Version information retrieval
• Application Management —
• List and filter applications by project, name, namespace

Tools it exposes

Once connected, the assistant can call these 12 tools directly:

• get_user_info — Get the current user's info via api/v1/session/userinfo
• get_settings — Get ArgoCD server settings including UI, OIDC, and other configurations
• get_plugins — Get information about configured ArgoCD plugins
• get_version — Get version information of the API server
• list_applications — Get all applications with filtering options
• get_application_details — Get detailed information about a specific application
• create_application — Create a new application
• update_application — Update an existing application
• delete_application — Delete an application
• sync_application — Trigger a sync operation on an application
• Setup — The Setup tool exposed by this server
• Requirements — The Requirements tool exposed by this server

Installing the argocd mcp mcp server

The server is distributed via PyPI as mypy, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 4 environment variables: ARGOCD_TOKEN, ARGOCD_API_URL, ARGOCD_VERIFY_SSL, YOUR_ARGOCD_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.12+ - MCP (includes FastMCP and development tools) - uv package manager (recommended) or pip - ArgoCD API token

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Argocd MCP sits in that group, and the shape of its toolset — get_user_info, get_settings, get_plugins among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 12 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Argocd MCP.
• Maintained by severity1, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the argocd mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.