Argo CD MCP Server

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/argocd-mcp-server

Source URLs

https://github.com/argoproj-labs/mcp-for-argocd#readme, https://github.com/argoproj-labs/mcp-for-argocd, https://argo-cd.readthedocs.io/en/stable/

Brand

Argo CD

Brand domain

argo-cd.readthedocs.io

Brand asset source

brandfetch

Safety notes

Argo CD MCP can inspect clusters, applications, resource trees, managed resources, workload logs, and resource events., By default all tools are available; setting MCP_READ_ONLY to true disables create_application, update_application, delete_application, sync_application, and run_resource_action., sync_application can apply changes to Kubernetes resources and may prune resources depending on options., delete_application can remove Argo CD applications and may cascade deletion to child resources depending on options., run_resource_action can trigger actions on resources managed by an application., Disabling TLS certificate validation with NODE_TLS_REJECT_UNAUTHORIZED weakens transport security and should be limited to reviewed development contexts.

Privacy notes

Argo CD application specs, cluster names, repository URLs, revisions, namespaces, Kubernetes manifests, resource events, and workload logs can reveal secrets, internal topology, deployment history, incident details, or customer data., ARGOCD_BASE_URL, ARGOCD_API_TOKEN, stateless HTTP request headers, cluster names, namespace names, and application names should stay out of prompts, issues, logs, screenshots, and committed files., Workload logs and resource events may include credentials, tokens, environment variables, error traces, or production incident context., HTTP transport should be authenticated and network-restricted so Argo CD tools are not reachable by untrusted clients.

Author

Argo Project Labs

Submitted by

oktofeesh1

Claim status

unclaimed

Last verified

2026-06-06

• Argo CD application specs, cluster names, repository URLs, revisions, namespaces, Kubernetes manifests, resource events, and workload logs can reveal secrets, internal topology, deployment history, incident details, or customer data.
• ARGOCD_BASE_URL, ARGOCD_API_TOKEN, stateless HTTP request headers, cluster names, namespace names, and application names should stay out of prompts, issues, logs, screenshots, and committed files.
• Workload logs and resource events may include credentials, tokens, environment variables, error traces, or production incident context.
• HTTP transport should be authenticated and network-restricted so Argo CD tools are not reachable by untrusted clients.

• Node.js 18 or newer.
• Argo CD instance with API access.
• Argo CD API token scoped to the minimum applications, projects, clusters, and actions Claude should use.
• Read-only mode enabled unless the workflow explicitly needs application or resource mutations.
• TLS and network-access review before disabling certificate verification or exposing HTTP transport.
• Human approval policy for sync, prune, delete, create, update, and run-resource-action operations.

Show that Argo CD MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/argocd-mcp-server.svg)](https://heyclau.de/entry/mcp/argocd-mcp-server)

Argo CD MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Argo CD MCP Server Argo Project Labs MCP server for connecting Claude to Argo CD applications, clusters, managed resources, workload logs, events, sync operations, and resource actions through stdio or HTTP stream transports. Open dossier	Coolify MCP Server MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search. Open dossier	gcloud MCP Server Google Cloud gcloud MCP server from googleapis that lets Claude run approved gcloud CLI commands with allowlist and denylist controls for cloud resource inspection, automation, and operations. Open dossier	Memory Bank MCP Server MCP server for remote project memory-bank management, with multi-project directories, file listing, read/write/update tools, and path isolation. Open dossier
Next steps	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust	Review first	Review first	Review first	Review first
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
Submitter	oktofeesh1	oktofeesh1	oktofeesh1	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Argo CD	Coolify MCP Server	gcloud MCP Server	—
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	Argo Project Labs	Stuart Mason	Google APIs	Aliosh Pimenta
Added	2026-06-06	2026-06-06	2026-06-06	2026-06-06
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Harness	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Argo CD MCP can inspect clusters, applications, resource trees, managed resources, workload logs, and resource events. By default all tools are available; setting MCP_READ_ONLY to true disables create_application, update_application, delete_application, sync_application, and run_resource_action. sync_application can apply changes to Kubernetes resources and may prune resources depending on options. delete_application can remove Argo CD applications and may cascade deletion to child resources depending on options. run_resource_action can trigger actions on resources managed by an application. Disabling TLS certificate validation with NODE_TLS_REJECT_UNAUTHORIZED weakens transport security and should be limited to reviewed development contexts.	✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions. Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once. Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation. Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually. Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure.	✓gcloud MCP Server executes gcloud CLI commands with the permissions of the active gcloud account. Allowed commands can create, update, delete, deploy, scale, list, export, or configure Google Cloud resources depending on IAM permissions and selected services. The server blocks command substitution, pipes, redirection, SSH-style commands, interactive commands, and a default set of sensitive command prefixes, but allowed gcloud commands can still have real infrastructure, billing, IAM, and data impact. Use allowlists for narrow workflows and service account impersonation with limited roles when possible. Require human approval for IAM, billing, networking, firewall, storage, database, secret, deployment, delete, and production-impacting commands.	✓Memory Bank MCP can read, create, and update files inside the configured memory-bank root. Do not point `MEMORY_BANK_ROOT` at a home directory, source repository root, cloud-sync folder, or any directory containing secrets. Avoid auto-approving write and update tools until the expected file structure and naming rules are established. The path validator rejects path traversal and slash-containing file/project names, but users should still keep the root directory narrow and dedicated. Docker mode requires a bind mount for the memory bank; review the host path and container path before granting write access.
Privacy notes	✓Argo CD application specs, cluster names, repository URLs, revisions, namespaces, Kubernetes manifests, resource events, and workload logs can reveal secrets, internal topology, deployment history, incident details, or customer data. ARGOCD_BASE_URL, ARGOCD_API_TOKEN, stateless HTTP request headers, cluster names, namespace names, and application names should stay out of prompts, issues, logs, screenshots, and committed files. Workload logs and resource events may include credentials, tokens, environment variables, error traces, or production incident context. HTTP transport should be authenticated and network-restricted so Argo CD tools are not reachable by untrusted clients.	✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client. Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors. Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials. Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance. Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs.	✓gcloud output can reveal project IDs, resource names, regions, IAM bindings, service accounts, logs, errors, labels, metadata, URLs, secrets references, billing context, and infrastructure topology. Authentication state, ADC files, service account impersonation details, access tokens, project IDs, and local gcloud configuration should stay out of prompts and repository files. Command output may be retained by the MCP client, model provider, terminal logs, shell history, and chat transcripts. Avoid broad listing or export commands against production projects unless data handling and retention have been reviewed.	✓Memory-bank files can contain project plans, architecture notes, decisions, credentials accidentally pasted into notes, customer context, meeting details, or personal information. Tool calls may expose project names, file names, memory contents, root-path assumptions, and update text to the MCP client and model provider. Multi-project listing can reveal all projects stored under the memory-bank root. Auto-approved memory tools can persist model-generated statements as project memory without human review. Back up important memory-bank directories and review retention expectations before sharing them across clients or machines.
Prerequisites	Node.js 18 or newer. Argo CD instance with API access. Argo CD API token scoped to the minimum applications, projects, clusters, and actions Claude should use. Read-only mode enabled unless the workflow explicitly needs application or resource mutations.	Running Coolify instance with API access enabled. Coolify API access token scoped to the resources Claude may inspect or manage. Node.js 20 or newer for the published npm server. Review of which servers, projects, applications, databases, services, deployments, env vars, private keys, teams, cloud tokens, and scheduled tasks the token can access.	Node.js 20 or newer with npm or another compatible package runner. Google Cloud CLI installed and authenticated. Active gcloud account, project, and configuration scoped to the intended environment. Least-privilege user or service account impersonation for the allowed cloud actions.	Node.js and npm available for `npx`. A dedicated memory-bank root directory, separate from source repositories and secrets. Project-specific subdirectories created under `MEMORY_BANK_ROOT`. MCP client approval rules reviewed before allowing write or update operations.
Install	npx argocd-mcp@latest stdio Copy install	npx -y @masonator/coolify-mcp Copy install	npx -y @google-cloud/gcloud-mcp Copy install	MEMORY_BANK_ROOT=ABSOLUTE_PATH_TO_MEMORY_BANK npx -y @allpepper/memory-bank-mcp@latest Copy install
Config	{ "mcpServers": { "argocd-mcp": { "command": "npx", "args": ["argocd-mcp@latest", "stdio"], "env": { "ARGOCD_BASE_URL": "<argocd-url>", "ARGOCD_API_TOKEN": "<argocd-token>", "MCP_READ_ONLY": "true" } } } } Copy config	{ "mcpServers": { "coolify": { "command": "npx", "args": [ "-y", "@masonator/coolify-mcp" ], "env": { "COOLIFY_BASE_URL": "https://your-coolify-instance.example", "COOLIFY_ACCESS_TOKEN": "your-api-token" }, "type": "stdio" } } } Copy config	{ "mcpServers": { "gcloud": { "command": "npx", "args": [ "-y", "@google-cloud/gcloud-mcp" ], "type": "stdio" } } } Copy config	Manual-only setup: MEMORY_BANK_ROOT=ABSOLUTE_PATH_TO_MEMORY_BANK npx -y @allpepper/memory-bank-mcp@latest Copy config
Citations	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationgithub.com Websiteargo-cd.readthedocs.io Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed

Source-backed guides for putting this to work.

• Comparison: CircleCI vs Azure DevOps vs Argo CD MCP servers for ClaudeOpen 3 picks in the interactive comparison tool