Argo CD MCP server

What the model can do

Argo CD (self-hosted): applications with their sync and health status, one application's resources, deployment history and conditions, its Kubernetes events, who committed a deployed revision, projects and clusters. Can create, sync, roll back, re-point to another revision or delete an application, stop a running sync, and run a resource action (such as restarting a Deployment) or delete one resource when asked.

Reads

• argocd_list_applicationsArgo CD applications with their sync status (Synced, OutOfSync), health (Healthy, Degraded, Progressing…), source repository and target…
• argocd_get_applicationOne Argo CD application in detail: status, conditions (errors and warnings), its Kubernetes resources with their sync and health (problems first)…
• argocd_application_eventsKubernetes events for an Argo CD application and its resources, newest first: warnings such as failed pulls, crash loops or failed syncs.
• argocd_revision_metadataWho committed a revision an Argo CD application deploys, when, and the commit message and tags (git sources).
• argocd_list_projectsArgo CD projects: description, which repositories and destinations each may deploy from and to, and its role names.
• argocd_list_clustersKubernetes clusters registered in Argo CD: name, API server, Kubernetes version, connection status and how many applications each runs.

Acts, when you ask

These change something in Argo CD. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• argocd_sync_applicationDeploys, sync an Argo CD application, applying its target revision (or the revision given) to its cluster.
• argocd_rollback_applicationDeploys an older revision, roll an Argo CD application back to an earlier deployment by its history id (argocd_get_application lists them).
• argocd_delete_applicationDeletes, delete an Argo CD application.
• argocd_terminate_operationStops a deployment, terminate the sync or rollback currently running on an Argo CD application.
• argocd_run_resource_actionChanges the cluster, run an Argo CD resource action on one resource of an application, e.g. "restart" on a Deployment, StatefulSet or DaemonSet…
• argocd_set_target_revisionMay deploy, point an Argo CD application at another Git revision (branch, tag or commit; or chart version).
• argocd_delete_resourceDeletes from the cluster, delete one Kubernetes resource an Argo CD application manages (identify it with the group, version, kind…
• argocd_create_applicationCreate an Argo CD application that deploys a repository path (or Helm chart) to a cluster namespace, in the project given.

Connect it

First connect Argo CD on Dashboard → Connections, then add Memtro to your client once. The Argo CD tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Argo CD connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which applications are out of sync or degraded?
• › What was deployed to production today, and who committed it?
• › Why is the payments app degraded?
• › Which clusters are registered and how many applications does each run?
• › Restart the api Deployment in the checkout application

Questions

Is this an official Argo CD MCP server?

No. It is Memtro's MCP server with Memtro's Argo CD connector behind it: the connector reads Argo CD through its API with the credentials you connect on Dashboard → Connections, and Argo CD publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Argo CD?

Only when you ask, and only what it has been granted: sync an application to its target revision (deploys to its cluster, never prunes); roll an application back to an earlier deployment (deploys that revision, never prunes); delete an application, leaving its Kubernetes resources running unless cascade is asked for; stop the sync or rollback running on an application; run a resource action, such as restarting a Deployment; point an application at another Git revision (deploys at once if auto-sync is on); delete one Kubernetes resource an application manages; create an application from a repository path or chart (no automatic sync). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server