Argo CD MCP Server: Setup for Claude Code, Cursor and Other Apps

• Lists your Argo CD applications, with optional search

  Returns the applications Argo CD manages. You can search by name and page through long lists to keep results short.

  Try: “List the Argo CD applications with "payments" in the name.”

  Network · list_applications

• Shows the details of one application

  Returns the full record for an application, including its source, destination and sync state.

  Try: “Show me the details of the checkout application.”

  Network · get_application

• Lists the clusters registered with Argo CD

  Returns registered clusters, which you can filter by name or server address.

  Try: “Which clusters does Argo CD deploy to?”

  Network · list_clusters

• Shows the details of one Argo CD project

  Returns the settings of a project, such as what repos and clusters it allows.

  Try: “Show the settings of the platform project.”

  Network · get_appproject

• Shows the tree of resources an application runs

  Returns the resources the application created, laid out from parent to child.

  Try: “Show the resource tree for the checkout application.”

  Network · get_application_resource_tree

• Lists the resources an application manages

  Returns the cluster resources Argo CD tracks for an application.

  Try: “Which resources does checkout manage?”

  Network · get_application_managed_resources

• Reads logs from an application's pods and workloads

  Fetches log lines from the workloads behind an application.

  Try: “Show the latest logs from the checkout pods.”

  Network · get_application_workload_logs

• Shows recent events for an application

  Returns the events Argo CD recorded for an application.

  Try: “What happened to the checkout application today?”

  Network · get_application_events

• Shows recent events for one resource

  Returns events for a single resource that an application manages, such as one deployment.

  Try: “Show events for the checkout deployment.”

  Network · get_resource_events

• Fetches the manifests of an application's resources

  Returns the live definitions of resources managed by an application.

  Try: “Show the manifest of the checkout service.”

  Network · get_resources

• Lists the actions a resource supports

  Shows which actions Argo CD offers for a resource, such as restart.

  Try: “What actions can I run on the checkout deployment?”

  Network · get_resource_actions

• Creates a new Argo CD application

  Creates an application in the namespace you give. Hidden when read-only mode is on.

  Try: “Create an application for the repo my-org/api in the staging cluster.”

  Write · create_application

• Changes an existing application

  Updates an application's definition. Hidden when read-only mode is on.

  Try: “Point the checkout application at the release branch.”

  Write · update_application

• Deletes an application

  Removes an application from Argo CD. You can choose whether the deletion cascades to the resources it created. Hidden when read-only mode is on.

  Try: “Delete the old demo application.”

  Delete · delete_application

• Syncs an application to match its source

  Applies the source state to the cluster. It supports a dry run, pruning of resources no longer in the source, and a chosen revision. Hidden when read-only mode is on.

  Try: “Sync checkout with a dry run first.”

  Delete · sync_application

• Runs an action on a resource

  Runs one of the actions a resource offers, such as restarting a deployment. Hidden when read-only mode is on.

  Try: “Restart the checkout deployment.”

  Write · run_resource_action

Watch out for

• It can delete applications and their resources

  Delete can cascade to child resources, and sync can prune resources. Turn on read-only mode unless you need changes. github.com

• It can run actions on live workloads

  The resource action tool runs actions such as restarts on the cluster. Review each call before approving it. github.com

• The network modes need a lock

  The README says the HTTP and SSE modes bind to loopback by default, and widening that needs MCP_AUTH_TOKEN or an explicit no-auth flag. Do not expose the port without one. github.com

• The README suggests turning off certificate checks

  For self-signed certificates it shows setting NODE_TLS_REJECT_UNAUTHORIZED to 0. Use that only in development. github.com

Security advisories