This server provides read-only access to one or more Argo CD instances via MCP, allowing you to inspect and query GitOps deployments without making any changes. Authentication uses browser session cookies and multiple instances are supported.

Connections & Instance Info

• list_connections – View all configured Argo CD instances (name, URL, description)

• get_version – Retrieve the Argo CD version of a specific instance

• get_settings – Fetch the global settings of a specific Argo CD instance

Applications

• list_applications – List all applications, optionally filtered by project names or label selectors

• get_application – Get detailed info on a specific app (sync status, health, spec)

• get_application_resource_tree – View the full Kubernetes resource tree and relationships for an app

• get_application_managed_resources – List managed resources, filterable by API group, kind, namespace, or resource name

• get_application_logs – Retrieve pod logs, with options for pod/container filtering, tail lines, and time window

Projects

• list_projects – List all Argo CD projects

• get_project – Get detailed project info including source repos, destinations, and roles

Clusters

• list_clusters – List all registered Kubernetes clusters and their connection status

• get_cluster – Get detailed info about a specific cluster by server URL

Repositories

• list_repositories – List all configured Git/Helm repositories and their connection status

• get_repository – Get detailed info about a specific repository by URL

Provides read-only access to Argo CD instances using browser session cookies, enabling listing applications, projects, clusters, repositories, and retrieving application details, resource trees, managed resources, and logs.

1. Click on "Install Server".

2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.

3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-read-only-argocd List all applications in staging."

That's it! The server will respond to your query, and you can continue using it as needed.

Here is a step-by-step guide with screenshots.

# Run the published package without cloning the repository
uvx mcp-read-only-argocd@latest --write-sample-config

# Or install it once and reuse the command directly
uv tool install mcp-read-only-argocd
mcp-read-only-argocd --write-sample-config

uvx mcp-read-only-argocd@latest --print-paths

- connection_name: staging
 url: https://argocd.example.com
 description: Staging Argo CD
 session_token: your-session-token

- connection_name: production
 url: https://argocd-prod.example.com
 description: Production Argo CD
 session_token: your-other-session-token

claude mcp add mcp-read-only-argocd \
 --scope user \
 -- uvx mcp-read-only-argocd@latest

codex mcp add mcp-read-only-argocd \
 -- uvx mcp-read-only-argocd@latest

List all applications in the staging Argo CD instance.

- connection_name: staging
 url: https://argocd.example.com
 description: Staging Argo CD instance
 session_token: your-session-token
 timeout: 30
 verify_ssl: true

# Show the resolved runtime paths
uvx mcp-read-only-argocd@latest --print-paths

# Write or refresh the default connections.yaml
uvx mcp-read-only-argocd@latest --write-sample-config
uvx mcp-read-only-argocd@latest --write-sample-config --overwrite

# Run the server with the default home-directory config
uvx mcp-read-only-argocd@latest

# Or point at a different runtime root
uvx mcp-read-only-argocd@latest --config-dir /path/to/config-dir

git clone https://github.com/lukleh/mcp-read-only-argocd.git
cd mcp-read-only-argocd
uv sync --extra dev
uv run pytest -q
uv run mcp-read-only-argocd --print-paths
uv run python smoke_test.py --print-paths

Looking for Admin?