get_user_infoLABSCO SUMMARY
Read the drift and fix it in the same conversation.
The application tools cover the loop that matters day to day: list what is OutOfSync or Degraded, open the one that looks wrong, then sync it. Creating and deleting applications is in the same set, so give the token the scope you would give a person doing that, and check get_user_info to see which account it maps to.
What it is
An MCP server for ArgoCD, the GitOps continuous-delivery controller for Kubernetes. It wraps the ArgoCD REST API so an assistant can answer "what is out of sync in production" and act on the answer, with the API token supplied once through the environment instead of pasted into every request.
What you get
- Applications listed with filters on project, name and namespace, and one application's full detail —
list_applications,get_application_details - Applications created, changed and removed —
create_application,update_application,delete_application - A sync triggered on an application, returning the resources it updated and the operation status —
sync_application - The identity the token resolves to, so you can confirm which account the agent is acting as —
get_user_info - Server settings including UI, OIDC and cluster configuration, the configured plugins, and the API server version —
get_settings,get_plugins,get_version
Requirements
An ArgoCD API token in ARGOCD_TOKEN and your endpoint in ARGOCD_API_URL — the default points at an example host, so it will not work until you set it. Python 3.12+ and the uv package manager; install with uv pip install -e . and run uv run server.py. For self-signed certificates set ARGOCD_VERIFY_SSL to false. Tokens are masked in the server's own logging. mcp dev server.py opens the MCP Inspector for debugging.
Setup effort
Build from source — git clone https://github.com/severity1/argocd-mcp.git
USE CASES
01
Finding what is out of sync in one project
List applications filtered to the project and read the sync and health status of each, instead of opening the ArgoCD UI per app.
02
Getting a stuck service back in line
Open the application's details to see why it drifted, then trigger a sync and read back which resources were updated.
03
Confirming what the agent is allowed to touch
Resolve the token to its user before granting anything broader, so the account behind the automation is not a guess.
04
Checking the cluster's ArgoCD configuration
Read the server settings, the installed plugins and the API server version together when diagnosing a behaviour difference between environments.
10 tools
Listed in project docs. Your client may show a different list.
get_settingsget_pluginsget_versionlist_applicationsget_application_detailscreate_applicationupdate_applicationdelete_applicationsync_applicationBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- Python 3.12+
- ARGOCD_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/severity1/argocd-mcp.git
cd argocd-mcp
uv venv
source .venv/bin/activate
uv pip install -e .
export ARGOCD_TOKEN=<YOUR_ARGOCD_TOKEN>
uv run server.pyMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add argocd-mcp -e ARGOCD_TOKEN=<YOUR_ARGOCD_TOKEN> -- "uv run $(pwd)/server.py"Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"argocd-mcp": {
"command": "<YOUR_PATH_TO_UV>",
"args": [
"--directory",
"<YOUR_PATH_TO_ARGOCD_MCP>",
"run",
"server.py"
],
"env": {
"ARGOCD_TOKEN": "<YOUR_ARGOCD_TOKEN>",
"ARGOCD_API_URL": "<YOUR_ARGOCD_URL>/api/v1",
"ARGOCD_VERIFY_SSL": "true"
}
}
}
}
