Tools reference
The ArgoCD MCP Server provides 29 tools organized across four operational domains: Application Management, Deployment & Sync Operations, Repository Onboarding, and Project Multi-Tenancy. Fourteen tools operate in read-only mode (MCP_ALLOW_WRITE=false), while 15 mutating tools require MCP_ALLOW_WRITE=true.
| Category | Total Tools | Read-Only (MCP_ALLOW_WRITE=false) | Write Required (MCP_ALLOW_WRITE=true) |
|---|---|---|---|
| Application Management | 7 | 4 | 3 |
| Deployment & Sync Operations | 10 | 3 (+ dry_run sync) | 7 |
| Repository Management | 7 | 4 | 3 |
| Project & RBAC Management | 5 | 3 | 2 |
| Total | 29 | 14 | 15 |
Application management tools (7)
| Tool | Write Required | Description |
|---|---|---|
list_applications | No | List all applications across clusters with health and sync states |
get_application_details | No | Retrieve detailed status, resource tree, and sync history for an application |
create_application | Yes | Create a new ArgoCD Application from a registered Git repository |
update_application | Yes | Update target revision, sync policies (automated, selfHeal, prune), or Helm parameters |
delete_application | Yes | Delete an ArgoCD Application (with optional cascade resource deletion) |
validate_application_config | No | Validate an application specification before creation |
get_application_events | No | Retrieve Kubernetes resource events associated with an application |
list_applications
Lists applications filtered by cluster, project, or namespace along with their current sync.status (Synced, OutOfSync) and health.status (Healthy, Progressing, Degraded).
get_application_details
Returns the complete resource tree, replica readiness, target Git revision, and recent deployment history for a single application.
create_application
Creates a declarative ArgoCD Application pointing to a Git repository path or Helm chart and binds it to a destination cluster, namespace, and AppProject.
Deployment and sync operations (10)
| Tool | Write Required | Description |
|---|---|---|
sync_application | Yes (No if dry_run=True) | Synchronize an application to its desired Git state |
get_application_diff | No | Compute the live vs. desired manifest diff before syncing |
get_sync_status | No | Inspect active or most recent sync operation phases and resource results |
rollback_application | Yes | Roll back an application to its immediately preceding successful revision |
rollback_to_revision | Yes | Roll back an application to a specific history ID or Git commit SHA |
get_application_logs | No | Fetch pod logs for an application with automatic error-pattern extraction |
prune_resources | Yes | Prune orphaned Kubernetes resources no longer present in Git |
hard_refresh | Yes | Invalidate the ArgoCD Git manifest cache and re-evaluate application state |
soft_refresh | Yes | Trigger a standard state reconciliation against the cached Git revision |
cancel_deployment | Yes | Terminate an in-progress sync operation |
sync_application
Synchronizes an application to its target Git revision.
app_name(string, required): Target ArgoCD application name.revision(string, optional): Specific Git branch, tag, or commit SHA.dry_run(boolean, default:False): Preview the sync result without mutating cluster resources (permitted even whenMCP_ALLOW_WRITE=false).prune(boolean, default:False): Delete resources that were removed from Git.
get_application_diff
Returns a structured resource-by-resource diff comparing the live Kubernetes manifests in the cluster against the desired manifests rendered from Git.
rollback_application & rollback_to_revision
Reverts an application to a known-good historical deployment revision. When automated sync (selfHeal) is enabled on the application, disable auto-sync via update_application prior to rolling back so ArgoCD does not immediately re-sync HEAD.
Repository management tools (7)
| Tool | Write Required | Description |
|---|---|---|
onboard_repository_https | Yes | Register a Git repository using server-side HTTPS credentials (GIT_PASSWORD) |
onboard_repository_ssh | Yes | Register a Git repository using server-side SSH keys (SSH_PRIVATE_KEY_PATH) |
list_repositories | No | List all Git and Helm repositories registered in ArgoCD |
get_repository | No | Inspect connection status and metadata for a specific repository URL |
validate_repository_connection | No | Test connectivity and authentication to a repository before registering it |
delete_repository | Yes | Remove a repository registration from ArgoCD |
generate_repository_secret_manifest | No | Generate a declarative v1/Secret YAML manifest (argocd.argoproj.io/secret-type: repository) |
Project and multi-tenancy tools (5)
| Tool | Write Required | Description |
|---|---|---|
create_project | Yes | Create an AppProject with scoped source repos, destination clusters/namespaces, and RBAC |
list_projects | No | List all configured ArgoCD projects |
get_project | No | Inspect allowed sources, destinations, and resource restrictions for a project |
delete_project | Yes | Delete an AppProject |
generate_project_manifest | No | Render a declarative AppProject CRD YAML manifest for GitOps version control |