mcp-argocd
Summary: An MCP server for the Argo CD REST API that lets AI assistants triage, sync, roll back, and inspect GitOps applications and their supporting infrastructure (37 tools, 7 resources, 7 prompts).
Triage applications — inspect spec, sync/health, conditions, operation status, events, resource trees, and pod logs.
Inspect drift — compare live vs desired managed resources, view rendered manifests, revision metadata, and deployment history.
Sync & roll back — trigger syncs (with prune/force/dry-run/selectors), roll back to history entries, terminate hung operations, and wait for completion.
Manage applications — create, patch, delete, and run custom resource actions (e.g. restart) on apps and managed resources.
Handle ApplicationSets — list/get them and dry-run generators to preview generated apps.
Query platform objects — list projects, clusters (invalidate cache), repositories (branches/tags/paths), server version, user identity, RBAC checks (
can_i), and settings.Guide the model — 7 curated resources (sync safety, rollback, GitOps flow, RBAC) and 7 workflow prompts (triage, diagnose sync failure, review drift, safe sync, rollback, fleet status, inspect ApplicationSet).
Run safely — locked read-only mode hides write tools, secrets are scrubbed, and destructive writes require user interaction approval.
Provides tools for interacting with the Argo CD REST API, enabling AI assistants to triage application status, sync, roll back, inspect drift, read logs, and manage ApplicationSets, clusters, projects, and repositories.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-argocd check the sync and health status of my guestbook app"
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.
mcp-argocd
mcp-argocd is a Model Context Protocol (MCP) server for the Argo CD REST API. It gives AI assistants 37 tools, 7 resources, and 7 prompts to triage application status, sync, roll back, inspect drift, read logs, and manage ApplicationSets, clusters, projects, and repositories. Works with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client. Runs in one of two modes: with writes, or locked read-only (MCP_READ_ONLY=true) so the 9 write tools are never offered to the model.
Works with Argo CD 3.3+ (any install: OSS, Akuity, OpenShift GitOps). Needs an API token, no cluster access.
Supports the MCP 2026-07-28 specification, often called MCP 2.0, and stays compatible with 2025-11-25 clients.
Built with FastMCP 4.x, httpx, and Pydantic.
Install: uvx mcp-argocd | PyPI | MCP Registry | Changelog
uvx mcp-argocd # with writes
MCP_READ_ONLY=true uvx mcp-argocd # locked read-only: write tools are not listed1-Click Installation
Claude Code plugin — one command adds the fleet marketplace, the next installs the server, prompts for ARGOCD_URL/ARGOCD_TOKEN (the token is stored in the credential store, never written to a config file), and keeps it updated:
claude plugin marketplace add vish288/.github
claude plugin install mcp-argocd@vish288-mcpTip: For other AI assistants (Claude Code, Windsurf, IntelliJ, Gemini CLI), visit the Argo CD MCP Installation Gateway.
Prerequisite: Install
uvfirst. Install uv.
Claude Code
# with writes
claude mcp add argocd -e ARGOCD_URL=https://argocd.example.com -e ARGOCD_TOKEN=<token> -- uvx mcp-argocd
# locked read-only
claude mcp add argocd -e MCP_READ_ONLY=true -e ARGOCD_URL=https://argocd.example.com -e ARGOCD_TOKEN=<token> -- uvx mcp-argocdWindsurf & IntelliJ
Windsurf: Add to ~/.codeium/windsurf/mcp_config.json
IntelliJ: Add to Settings | Tools | MCP Servers
Remove MCP_READ_ONLY to allow writes.
{
"mcpServers": {
"argocd": {
"command": "uvx",
"args": ["mcp-argocd"],
"env": {
"ARGOCD_URL": "https://argocd.example.com",
"ARGOCD_TOKEN": "<token>",
"MCP_READ_ONLY": "true"
}
}
}
}Gemini CLI
The repo ships gemini-extension.json; install it with the Gemini CLI extension flow, or add it directly:
# with writes
gemini mcp add -s user -e ARGOCD_URL=https://argocd.example.com -e ARGOCD_TOKEN=<token> argocd uvx mcp-argocd
# locked read-only
gemini mcp add -s user -e MCP_READ_ONLY=true -e ARGOCD_URL=https://argocd.example.com -e ARGOCD_TOKEN=<token> argocd uvx mcp-argocdVS Code
Add to .vscode/mcp.json. Remove MCP_READ_ONLY to allow writes.
{
"servers": {
"argocd": {
"type": "stdio",
"command": "uvx",
"args": ["mcp-argocd"],
"env": {
"ARGOCD_URL": "https://argocd.example.com",
"ARGOCD_TOKEN": "<token>",
"MCP_READ_ONLY": "true"
}
}
}
}Codex
# with writes
codex mcp add argocd --env ARGOCD_URL=https://argocd.example.com --env ARGOCD_TOKEN=<token> -- uvx mcp-argocd
# locked read-only
codex mcp add argocd --env MCP_READ_ONLY=true --env ARGOCD_URL=https://argocd.example.com --env ARGOCD_TOKEN=<token> -- uvx mcp-argocdpip / uv
uvx mcp-argocd # run without installing
pip install mcp-argocd # or install into an environmentDrop MCP_READ_ONLY to allow writes. On a shared or hosted server put it in the deployer's env, not the client config.
Related MCP server: ArgoCD MCP Server
Configuration
Variable | Required | Default | Description |
| Yes | - | Base URL including any path prefix. Also reads |
| Yes | - | Bearer token. Also reads |
| No |
| Shared name across the mcp-* servers. Any value other than |
| No |
| Per-server alias for |
| No | all | Comma list of tool groups to expose (see Toolsets); unset or |
| No | - | Bearer token (min 16 chars) required to bind an HTTP transport to a non-loopback host; clients send |
| No |
| Request timeout in seconds |
| No |
|
|
| No | - | Default |
Toolsets
Clients cap how many tools they forward (Cursor warns past 40, across all servers). MCP_TOOLSETS
(or --toolsets) shrinks tools/list to one or more named groups; unset or all lists every
tool. Names are lowercase and comma-separated; an unknown name exits 2 with the valid list.
MCP_READ_ONLY still applies afterward and only ever removes more tools (the read-only column).
Group | Raw tags | Tools | Read-only |
| applications | 22 | 14 |
| applicationsets | 3 | 3 |
| projects, clusters, repositories, server | 12 | 11 |
| every tag | 37 | 28 |
MCP_TOOLSETS=apps,appsets uvx mcp-argocd # application + ApplicationSet tools only
uvx mcp-argocd --toolsets admin # projects, clusters, repositories, server settingsGetting an API token
Argo CD tokens come from a local account with the apiKey capability, or from a project role.
Add a local account in
argocd-cm: setaccounts.ci-bot: apiKey.Generate a token:
argocd account generate-token --account ci-bot --expires-in 24h.Set
ARGOCD_URLandARGOCD_TOKEN.
Minimum read-only RBAC:
p, role:mcp-ro, applications, get, */*, allow
p, role:mcp-ro, logs, get, */*, allow
p, role:mcp-ro, applicationsets, get, */*, allow
p, role:mcp-ro, projects, get, *, allow
p, role:mcp-ro, clusters, get, *, allow
p, role:mcp-ro, repositories, get, *, allowCompatibility
Component | Supported |
Argo CD | 3.3+ (OSS, Akuity, OpenShift GitOps); most tools also work on 2.x |
Python | 3.11, 3.12, 3.13, 3.14 |
Transports | stdio, streamable-http, sse (deprecated) |
MCP spec | 2026-07-28 (MCP 2.0); compatible with 2025-11-25 |
Protocol support
Supports the MCP 2026-07-28 specification (MCP 2.0) and stays compatible with 2025-11-25 clients.
Built on FastMCP 4.x. A regression test lists all 37 tools with an in-memory MCP client pinned to
2026-07-28. The sse transport is
deprecated by the 2026-07-28 specification; it still works and prints a warning. The server uses
no roots, sampling, logging, elicitation, or resource subscriptions.
serverInfo reports the installed package version and the install page as websiteUrl, so every
response names the exact release. List results (tools/list, prompts/list, resources/list)
carry the 2026-07-28 cache hints ttlMs: 300000 (5-minute TTL) and cacheScope: private — private
because resources/read can vary by the per-user token. Both are inert for clients that do not
read them.
Error results
Expected failures — a missing app (404), a denied permission (403), a write that reaches the
read-only guard — return a tool result with isError: true rather than a success envelope. (In
locked read-only mode the write tools are hidden, so calling one returns an Unknown tool error;
the envelope below is the guard's own response, returned only when a client reaches a write tool
anyway.) The body is a JSON
object {"error", "status_code"?, "body"?, "hint"?}, where hint names a corrective action when
one applies. The body is the result's pretty-printed text content; the result carries no
structuredContent, because a strict MCP client (the TypeScript SDK) validates structuredContent
against the tool's outputSchema even when isError is true and would reject the error otherwise.
Unexpected bugs are also isError: true but carry TypeName: message text and a logged traceback.
Successful results carry the same JSON object as structuredContent alongside the pretty-printed
text, so a client may read either. Tools advertise no outputSchema: payloads pass upstream fields
through untyped, and a typed schema is opt-in per tool via output_schema=.
Tools (37)
Category | Count |
Applications — read | 14 |
Applications — write | 8 |
ApplicationSets | 3 |
Projects | 2 |
Clusters | 3 |
Repositories | 3 |
Server and account | 4 |
Applications — read
argocd_list_applications— List applications with slim rows; filter by sync, health, destination.argocd_get_application— Get one application: spec, sync/health, conditions, operation, counts.argocd_get_resource_tree— Get the live resource tree as slim nodes.argocd_get_managed_resources— Get live-vs-desired diffs for managed resources.argocd_get_resource— Get a single managed resource's live manifest.argocd_get_manifests— Get the rendered desired manifests for a revision.argocd_get_application_events— Get Kubernetes events for an application.argocd_get_pod_logs— Get container logs; never follows.argocd_get_application_history— Get deployment history, newest first.argocd_get_revision_metadata— Get commit metadata for a revision.argocd_get_operation— Get the current or last sync operation.argocd_wait_for_operation— Poll until an operation is terminal, gone, or times out.argocd_get_sync_windows— Get sync windows and whether the app can sync now.argocd_list_resource_actions— List the custom actions available on a resource.
Applications — write
argocd_sync_application— Sync an application; prune and force can delete or recreate resources.argocd_rollback_application— Roll back to a prior deployment history entry.argocd_terminate_operation— Terminate the running sync operation.argocd_create_application— Create an application from flattened parameters.argocd_patch_application— Patch an application; the one tool for every update.argocd_delete_application— Delete an application.argocd_run_resource_action— Run a custom resource action, such as restart.argocd_delete_resource— Delete a single managed resource so the controller recreates it.
ApplicationSets
argocd_list_applicationsets— List ApplicationSets with slim rows.argocd_get_applicationset— Get one ApplicationSet and the status of its generated apps.argocd_generate_applicationset— Dry-run the generators to preview generated apps; creates nothing.
Projects
argocd_list_projects— List projects with slim rows.argocd_get_project— Get a project's repos, destinations, and roles.
Clusters
argocd_list_clusters— List clusters with connection state, versions, and counts.argocd_get_cluster— Get one cluster by name or server URL.argocd_invalidate_cluster_cache— Invalidate a cluster's cached resources.
Repositories
argocd_list_repositories— List repositories; credentials are never returned.argocd_get_repository_refs— Get a repository's branches and tags.argocd_list_repository_apps— List the application paths discoverable in a repository.
Server and account
argocd_get_version— Get the Argo CD server version and bundled tool versions.argocd_get_userinfo— Get the authenticated identity.argocd_can_i— Check whether the account may perform a resource/action.argocd_get_settings— Get server settings and enabled features.
Resources (7)
The server exposes curated GitOps rules and guides as MCP resources.
resource://rules/sync-safety— Sync Safety Rules.resource://rules/rollback— Rollback Rules.resource://rules/gitops-change-flow— GitOps Change Flow.resource://rules/applicationsets— ApplicationSet Rules.resource://guides/status-triage— Status Triage Guide.resource://guides/rbac— RBAC and Permission Errors.resource://guides/api-token-setup— API Token Setup.
Prompts (7)
The server provides MCP prompts — multi-tool workflow templates clients surface as slash commands.
triage_application— Diagnose a Degraded or OutOfSync application.diagnose_sync_failure— Classify why the last sync failed.review_drift— Review OutOfSync apps and recommend a fix.safe_sync— Check sync windows, dry-run, then sync and wait.rollback_application— Roll back with the auto-sync check.fleet_status— Report clusters and apps that are not Synced/Healthy.inspect_applicationset— Compare generated vs existing apps.
Usage Examples
Triage: "Why is
paymentsDegraded?" runstriage_application— app conditions, unhealthy nodes, warning events, then pod logs.Drift: "What has drifted in
prod?" runsreview_drift— lists OutOfSync apps and shows each diff.Safe sync: "Sync
websafely" runssafe_sync— checks sync windows, dry-runs, then syncs and waits.Rollback: "Roll
apiback to the last good deploy" runsrollback_application— checks auto-sync first.Fleet: "Show cluster health" runs
fleet_status— clusters and the apps that are not healthy.
Security Considerations
Token scope: use the minimum RBAC the workflow needs. A read-only role needs
applications, getandlogs, get.Read-only mode: set
MCP_READ_ONLY=true(orARGOCD_READ_ONLY=true) in the launch you control and the server starts locked: the 9 write tools and the write-workflow prompts are not listed, a call to one returns "Unknown tool", and the guard refuses any write that still reaches it. Nothing lifts the lock at runtime — not afalsefrom another source, not a.envfile, not tool arguments; any value other thanfalse/0/no/off/empty locks, and--read-onlycan only raise it. The lock is only as strong as the launch: set it where users cannot edit it (a managed MCP config such as Claude Codemanaged-mcp.json, a container, k8s or systemd env, or a hosted HTTP deployment). A user who starts the server themselves controls its environment. Pair it with a read-only Argo CD RBAC role (applications, get;logs, get).SSL verification: on by default. Disable only for self-signed certificates in trusted networks.
Secret scrubbing: repository, cluster, and project payloads are scrubbed of credentials, cluster
config, and rolejwtTokens, even withfull=True.MCP tool annotations: every tool declares
readOnlyHint,destructiveHint, andidempotentHint.No credential storage: the server reads the token from the environment at startup and never persists it.
Destructive tools:
argocd_sync_application,argocd_rollback_application,argocd_terminate_operation,argocd_delete_application,argocd_run_resource_action,argocd_delete_resource.Approval on state-changing writes: every write tool that can create or change live cluster state carries the
anthropic/requiresUserInteractionclient-vendor meta — the six destructive tools above plusargocd_create_applicationandargocd_patch_application(a create can deploy workloads via its sync policy; a patch can enable auto-sync or retarget a source). Claude Code forces a permission prompt on every call — even underacceptEdits,auto, andbypassPermissions— with no "don't ask again". Pure-read tools and the metadata-onlyargocd_invalidate_cluster_cache(it clears Argo CD's cache, changing nothing real) are not gated. The meta is inert for clients that do not read it.
Permissions
Operation | Argo CD RBAC |
Read apps and resources |
|
Read pod logs |
|
Sync |
|
Override a revision |
|
Roll back |
|
Delete an app |
|
Run a resource action |
|
Read clusters, projects, repos |
|
CLI & Transport Options
uvx mcp-argocd # stdio (default)
uvx mcp-argocd --transport streamable-http --port 9000
uvx mcp-argocd --transport sse # deprecated; prints a warning
uvx mcp-argocd --read-only --insecureAn HTTP transport serves every tool, with the owner's Argo CD token, to anyone who reaches the
port. Host/Origin protection is not authentication, so binding to a non-loopback host requires a
bearer token: set ARGOCD_HTTP_BEARER_TOKEN (min 16 chars; clients send Authorization: Bearer <token>). The server refuses to start on a non-loopback host without it.
ARGOCD_HTTP_BEARER_TOKEN=$(openssl rand -hex 32) \
uvx mcp-argocd --transport streamable-http --host 0.0.0.0 --port 9000Observability
An HTTP transport exposes GET /health, an unauthenticated liveness probe that returns the
server name and version (no config, no secrets) for container and load-balancer checks:
curl -s http://127.0.0.1:9000/health
# {"status":"ok","name":"Argo CD MCP Server","version":"0.7.1"}FastMCP emits OpenTelemetry spans for tools/call and propagates trace context by default — no
opt-in needed. Point it at a collector with the standard OTel environment and launch under the
auto-instrumentation wrapper:
OTEL_EXPORTER_OTLP_ENDPOINT=http://collector:4317 \
opentelemetry-instrument uvx mcp-argocd --transport streamable-http --port 9000Set FASTMCP_TELEMETRY_MODE=off to disable tracing entirely (propagation_only keeps trace-context
propagation without emitting spans).
Docker
The image defaults to locked read-only (MCP_READ_ONLY=true); pass -e MCP_READ_ONLY=false to allow writes.
docker build -t mcp-argocd .
# stdio, locked read-only (the image default)
docker run --rm -i \
-e ARGOCD_URL=https://argocd.example.com \
-e ARGOCD_TOKEN=<token> \
mcp-argocdThe image runs as a non-root user and defaults to stdio; pass
--transport streamable-http --host 0.0.0.0 (with ARGOCD_HTTP_BEARER_TOKEN) to serve over HTTP.
FAQ
Does mcp-argocd support MCP 2026-07-28 (MCP 2.0)? Yes. It supports the MCP 2026-07-28 specification, often called MCP 2.0, and stays compatible with 2025-11-25 clients.
How is it different from argoproj-labs/mcp-for-argocd? argoproj-labs/mcp-for-argocd is the official TypeScript server with 15 tools. mcp-argocd adds 37 tools with slim payloads by default, plus diff, rollback, terminate, wait-for-operation, ApplicationSet dry-run, and RBAC error hints.
Which Argo CD versions work? Argo CD 3.3 and newer. Most tools also work on 2.x; only run_resource_action uses a 3.x endpoint.
Does it need kubectl or cluster credentials? No. It talks to the Argo CD API over HTTPS with a bearer token. It never touches the cluster directly.
Can I run mcp-argocd read-only so the assistant cannot sync or delete anything? Yes. Start it with MCP_READ_ONLY=true (or ARGOCD_READ_ONLY=true). The 9 write tools and the write-workflow prompts are then not listed at all, so the model never sees them; a call to one returns "Unknown tool", and nothing can turn writes back on while the process runs. Set it in a launch you control — a managed MCP config, a container or systemd env, or a hosted deployment — because a user who starts the server themselves can start it without the variable.
Which token does it need? It needs a bearer token in ARGOCD_TOKEN. Generate one from a local account with the apiKey capability, or use a project-role token. It also reads ARGOCD_AUTH_TOKEN and ARGOCD_API_TOKEN.
Why do I get a 403 for an app that exists? Without project, Argo CD returns 403 for an app that does not exist. Pass project to get a real 404.
Can it sync only one resource? Yes. Pass resources to argocd_sync_application with [group:]kind:name[/namespace] selectors.
Can it roll back? Yes. Use argocd_rollback_application with a history id. It refuses while auto-sync is on and tells you how to disable it.
How does it keep responses small? Every tool returns a slim payload by default and pages lists client-side. Pass full=True for the raw payload.
Which transports? stdio, streamable-http, and sse. sse is deprecated by the 2026-07-28 spec but still works.
How do I install? Run uvx mcp-argocd, or add it to your MCP client config.
Related MCP Servers
mcp-gitlab — GitLab integration (83 tools, 7 resources, 6 prompts)
mcp-atlassian-extended — Jira + Confluence integration (22 tools, 15 resources, 5 prompts)
mcp-coda — Coda integration (53 tools, 12 resources, 5 prompts)
Development
git clone https://github.com/vish288/mcp-argocd.git
cd mcp-argocd
uv sync --all-extras
uv run pytest --cov
uv run ruff check .
uv run ruff format --check .Please read the contributing guide and the security policy before opening a pull request or reporting a vulnerability.
License
MIT — see LICENSE.
Available Tools
37 toolsargocd_can_iArgocd Can IBRead-onlyIdempotent
Check whether the current account may perform resource/action on a subresource.
Returns {allowed: bool, ...}; the API answers the string yes/no.
Inputs: action (required), resource (required), subresource.
argocd_create_applicationArgocd Create ApplicationA
Create an application from flattened parameters. Use patch for anything this does not cover.
Returns the created application, slim. Idempotent only with upsert=True.
Inputs: name (required), project (required), repo_url (required), path, +18 more.
argocd_delete_applicationArgocd Delete ApplicationBDestructive
Delete an application. destructive. cascade=False removes only the Application object.
Inputs: name (required), cascade, project, app_namespace, +1 more.
argocd_delete_resourceArgocd Delete ResourceBDestructive
Delete a single managed resource so the controller recreates it. destructive.
Inputs: kind (required), name (required), resource_name (required), force, +6 more.
argocd_generate_applicationsetArgocd Generate ApplicationsetARead-onlyIdempotent
Dry-run the generators: preview the applications an ApplicationSet would produce. Creates nothing. The manifest must be JSON.
Inputs: applicationset (required), appset_namespace.
argocd_get_applicationArgocd Get ApplicationARead-onlyIdempotent
Get one application: spec, sync/health, conditions, operation, summary, resource counts.
refresh=hard forces reconciliation and re-fetches target manifests from the repo server.
Inputs: name (required), full, project, refresh, +2 more.
argocd_get_application_eventsArgocd Get Application EventsARead-onlyIdempotent
Get Kubernetes events for an application, newest first, with messages capped at 500 chars.
Inputs: name (required), limit, offset, project, +5 more.
argocd_get_application_historyArgocd Get Application HistoryBRead-onlyIdempotent
Get deployment history (newest first) with revision, who deployed it, and the source.
Inputs: name (required), limit, offset, project, +1 more.
argocd_get_applicationsetArgocd Get ApplicationsetARead-onlyIdempotent
Get one ApplicationSet: generators, strategy, and the status of the apps it generates.
Inputs: name (required), full, appset_namespace, include_template, +1 more.
argocd_get_clusterArgocd Get ClusterARead-onlyIdempotent
Get one cluster by name or server URL. The credential config is always removed, even with full=True.
Inputs: cluster (required), full.
argocd_get_managed_resourcesArgocd Get Managed ResourcesARead-onlyIdempotent
Get managed resources with their live-vs-desired diffs (truncated by default).
include_states adds the parsed target, normalized-live, and predicted-live manifests with managedFields stripped.
Inputs: name (required), kind, group, project, +7 more.
argocd_get_manifestsArgocd Get ManifestsBRead-onlyIdempotent
Get the rendered desired manifests for a revision, parsed into objects and paged.
Inputs: name (required), kind, limit, offset, +4 more.
argocd_get_operationArgocd Get OperationARead-onlyIdempotent
Get the current or last sync operation: phase, who started it, and per-status result counts.
Returns {"phase": null} when no operation has run.
Inputs: name (required), project, app_namespace, include_resources.
argocd_get_pod_logsArgocd Get Pod LogsARead-onlyIdempotent
Get container logs (never follows). Returns lines with pod and timestamp, the pods seen, and a shown_lines count; stops at the stream's last marker.
Inputs: name (required), kind, group, filter, +10 more.
argocd_get_projectArgocd Get ProjectARead-onlyIdempotent
Get a project: allowed repos, destinations, resource whitelists/blacklists, and roles.
Role token values (jwtTokens) are never returned; only a token count.
Inputs: name (required), full, include_roles.
argocd_get_repository_refsArgocd Get Repository RefsARead-onlyIdempotent
Get a repository's branches and tags, each paged separately with its own counts.
Inputs: repo (required), limit, offset, app_project, +1 more.
argocd_get_resourceArgocd Get ResourceARead-onlyIdempotent
Get a single managed resource's live manifest, with managedFields and the last-applied annotation removed.
Inputs: kind (required), name (required), resource_name (required), full, +5 more.
argocd_get_resource_treeArgocd Get Resource TreeARead-onlyIdempotent
Get the live resource tree as slim nodes (kind, name, health, images, parent).
Drops networkingInfo, uid, and resourceVersion. Filters by kind and health client-side.
Inputs: name (required), kind, limit, offset, +5 more.
argocd_get_revision_metadataArgocd Get Revision MetadataBRead-onlyIdempotent
Get commit metadata for a revision: author, date, message, tags, signature info.
Inputs: name (required), revision (required), project, version_id, +2 more.
argocd_get_settingsArgocd Get SettingsARead-onlyIdempotent
Get server settings: URL, enabled features, tracking method, and plugin names.
Drops OIDC/Dex config and UI banner fields in the slim view.
Inputs: full.
argocd_get_sync_windowsArgocd Get Sync WindowsARead-onlyIdempotent
Get sync windows for an application: whether it can sync now, plus active and assigned windows.
Inputs: name (required), project, app_namespace.
argocd_get_userinfoArgocd Get UserinfoARead-onlyIdempotent
Get the authenticated identity: username, groups, whether logged in, and the token issuer.
Inputs: no named parameters.
argocd_get_versionArgocd Get VersionARead-onlyIdempotent
Get the Argo CD server version and its bundled tool versions. The connectivity probe.
Inputs: no named parameters.
argocd_invalidate_cluster_cacheArgocd Invalidate Cluster CacheAIdempotent
Invalidate a cluster's cached resources — the standard fix for phantom OutOfSync or Unknown health. Removes nothing real.
Inputs: cluster (required).
argocd_list_applicationsArgocd List ApplicationsARead-onlyIdempotent
List applications with slim rows (name, project, sync/health, source, destination, policy).
Filters sync_status, health_status, destination, and name_prefix client-side; the Argo CD list endpoint has no paging, so results are sorted by name and sliced here.
Inputs: repo, limit, offset, projects, +8 more.
argocd_list_applicationsetsArgocd List ApplicationsetsARead-onlyIdempotent
List ApplicationSets with slim rows (generators present, strategy, health, conditions).
Inputs: limit, offset, projects, selector, +1 more.
argocd_list_clustersArgocd List ClustersARead-onlyIdempotent
List clusters with slim rows (connection state, server version, app and cache counts).
The cluster credential config is never returned.
Inputs: name, limit, offset, server.
argocd_list_projectsArgocd List ProjectsBRead-onlyIdempotent
List projects with slim rows (repo/destination counts, role names, sync-window count).
Inputs: name, limit, offset.
argocd_list_repositoriesArgocd List RepositoriesARead-onlyIdempotent
List repositories with slim rows and connection state. Credentials are never returned; has_credentials reports whether any are configured.
Inputs: repo, limit, offset, app_project, +1 more.
argocd_list_repository_appsArgocd List Repository AppsBRead-onlyIdempotent
List the application paths (and their config type) discoverable in a repository.
Inputs: repo (required), limit, offset, revision, +1 more.
argocd_list_resource_actionsArgocd List Resource ActionsBRead-onlyIdempotent
List the custom resource actions available on a resource (e.g. restart, pause).
Inputs: kind (required), name (required), resource_name (required), group, +4 more.
argocd_patch_applicationArgocd Patch ApplicationAIdempotent
Patch an application — the one tool for every update.
Examples: change targetRevision with patch='{"spec":{"source":{"targetRevision":"v2"}}}'; disable auto-sync with patch='{"spec":{"syncPolicy":{"automated":null}}}'.
Inputs: name (required), patch (required), project, patch_type, +1 more.
argocd_rollback_applicationArgocd Rollback ApplicationADestructive
Roll back to a prior deployment history entry. destructive.
Argo CD refuses a rollback while auto-sync is on, so this pre-reads the app and returns an actionable error first. A rollback re-applies an old revision, so fix Git afterward.
Inputs: name (required), history_id (required), wait, prune, +4 more.
argocd_run_resource_actionArgocd Run Resource ActionCDestructive
Run a custom resource action (restart a Deployment, pause a Rollout). destructive.
Inputs: kind (required), name (required), action (required), resource_name (required), +6 more.
argocd_sync_applicationArgocd Sync ApplicationADestructive
Sync an application. destructive because prune and force can delete or recreate resources.
Returns the started operation; with wait=True, the final one. revision override needs the
applications, override RBAC permission.
Inputs: name (required), wait, force, prune, +9 more.
argocd_terminate_operationArgocd Terminate OperationADestructiveIdempotent
Terminate the running sync operation. Use to unstick a sync hanging in Running.
Inputs: name (required), project, app_namespace.
argocd_wait_for_operationArgocd Wait For OperationARead-onlyIdempotent
Poll an application until its operation reaches a terminal phase, disappears, or times out.
Never errors on timeout; returns timed_out=true with the latest operation, sync, and health.
Inputs: name (required), project, app_namespace, timeout_seconds, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 37 tools
Most tools have a clearly distinct resource+action target, and the read-heavy application tools (get_application, get_resource_tree, get_managed_resources, get_resource, get_manifests) are separated by descriptions explaining live vs desired vs single-resource scope. The only mild risk is confusion between the managed-resource/rendered-manifest readers and between list_applicationsets/get_applicationset, but the wording disambiguates them adequately.
Every tool follows the same argocd_verb_noun snake_case pattern (argocd_list_applications, argocd_get_application, argocd_patch_application, argocd_delete_resource). Exceptions like argocd_can_i and argocd_get_version still fit the prefix+verb convention, so the surface is highly predictable.
37 tools is heavy and above the comfortable band, but Argo CD is a genuinely broad domain (clusters, repos, projects, ApplicationSets, applications, resources, logs, operations) and most tools map to a distinct operation rather than duplicating each other. A few informational tools (get_version, get_settings, get_userinfo, can_i) could plausibly be consolidated, so it sits at the borderline rather than being well-scoped.
Application lifecycle is well covered (list/get/create/patch/delete plus sync, rollback, terminate, history, logs, events), and per-resource actions and deletion exist. However, there is no create/update/delete for projects, clusters, repositories, or ApplicationSets (generate_applicationset is dry-run only), leaving notable management gaps for a server whose stated scope spans those entities.
Maintenance
Related MCP Connectors
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Read and write KukGit repositories, files, issues and pull requests from an AI assistant.
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with ArgoCD APIs through standardized MCP tools for managing applications, resources, and deployments.MIT
- AlicenseAqualityCmaintenanceSafety-first GitOps operations for ArgoCD via the Model Context Protocol. Enables listing, diagnosing, syncing, and managing ArgoCD applications with progressive disclosure and defense-in-depth security.15Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications through natural language, providing tools for cluster, project, application, and resource management via stdio and HTTP transports.Apache 2.0