argocd-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_READ_ONLY | No | Set to 'true' to run the MCP Server in read-only mode, which disables resource modification tools | false |
| ARGOCD_BASE_URL | Yes | The base URL of your Argo CD instance | |
| ARGOCD_API_TOKEN | Yes | Your Argo CD API token for authentication | |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to '0' to disable TLS certificate validation for self-signed certificates. Warning: This reduces security and should only be used in development environments. | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_applicationsC | list_applications returns list of applications |
| get_applicationB | get_application returns application by application name. Optionally specify the application namespace to get applications from non-default namespaces. |
| get_application_resource_treeC | get_application_resource_tree returns resource tree for application by application name |
| get_application_managed_resourcesA | get_application_managed_resources returns managed resources for application by application name with optional filtering. Use filters to avoid token limits with large applications. Examples: kind="ConfigMap" for config maps only, namespace="production" for specific namespace, or combine multiple filters. |
| get_application_workload_logsC | get_application_workload_logs returns logs for application workload (Deployment, StatefulSet, Pod, etc.) by application name and resource ref and optionally container name |
| get_application_eventsC | get_application_events returns events for application by application name |
| get_resource_eventsC | get_resource_events returns events for a resource that is managed by an application |
| get_resourcesA | get_resources return manifests for resources specified by resourceRefs. If resourceRefs is empty or not provided, fetches all resources managed by the application. |
| get_resource_actionsC | get_resource_actions returns actions for a resource that is managed by an application |
| create_applicationC | create_application creates a new ArgoCD application in the specified namespace. The application.metadata.namespace field determines where the Application resource will be created (e.g., "argocd", "argocd-apps", or any custom namespace). |
| update_applicationD | update_application updates application |
| delete_applicationC | delete_application deletes application. Specify applicationNamespace if the application is in a non-default namespace to avoid permission errors. |
| sync_applicationC | sync_application syncs application. Specify applicationNamespace if the application is in a non-default namespace to avoid permission errors. |
| run_resource_actionC | run_resource_action runs an action on a resource |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct aspect of ArgoCD application management. While get_application_events and get_resource_events could be confused, descriptions clarify their scope. Overall, purposes are clearly separated.
All tools use consistent snake_case with verb_noun pattern (e.g., create_application, get_application_events). The naming is predictable and follows a clear convention.
14 tools is well-scoped for an ArgoCD MCP server, covering CRUD operations, synchronization, logs, events, and resource management without being excessive.
The tool set covers core application lifecycle (CRUD, sync, logs, events) and resource management. Minor gaps like rollback or version history are missing, but the surface is largely complete for common tasks.