What can argocd-mcp do?

argo cd application state synchronization via mcp, argo cd application state querying and monitoring, argo cd application creation and configuration management, argo cd repository and credential management, argo cd cluster registration and management, argo cd notification and event streaming, argo cd rollback and deployment history management, argo cd project and rbac policy management

argocd-mcp

MCP ServerFree

Argo CD MCP Server

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

argo cd application state synchronization via mcp

Medium confidence

Exposes Argo CD's application sync capabilities through the Model Context Protocol, allowing LLM agents to trigger and monitor application deployments by translating natural language intent into ArgoCD API calls. Implements MCP tool schema binding to map sync operations (sync, refresh, hard-refresh) to Argo CD gRPC/REST endpoints with real-time status polling.

Solves for

I want an AI agent to automatically sync my Argo CD applications when deployment conditions are metI need to trigger application synchronization from an LLM-based deployment assistant without manual kubectl accessI want to integrate Argo CD deployment workflows into an agentic system that can reason about GitOps state

Best for

DevOps teams building AI-assisted deployment orchestration

Platform engineers integrating Argo CD into LLM agent workflows

Organizations automating GitOps operations through conversational interfaces

Requires

Argo CD 2.0+ server instance with gRPC or REST API enabled

Valid Argo CD authentication token or credentials

Network access from MCP server to Argo CD API endpoint

Limitations

Requires network connectivity to Argo CD server; no local caching of application state

Sync operations are asynchronous but MCP tool responses are synchronous, requiring polling or callback patterns for completion status

No built-in retry logic or exponential backoff for failed sync operations

What makes it unique

Bridges Argo CD's declarative GitOps model with agentic decision-making by exposing sync operations as MCP tools, enabling LLMs to reason about and trigger deployments without direct kubectl access or custom API wrappers

vs alternatives

Provides native MCP integration for Argo CD workflows, whereas alternatives typically require custom REST API clients or kubectl plugins that lack semantic understanding of deployment intent

argo cd application state querying and monitoring

Medium confidence

Implements MCP resource handlers to query live application state from Argo CD, including sync status, health, resource tree, and deployment history. Uses Argo CD's gRPC or REST API to fetch structured application metadata and translates it into LLM-consumable formats for reasoning about deployment health and readiness.

Solves for

I want to ask an AI agent about the current deployment status of my applications without logging into Argo CD UII need to check if an application is healthy and synced before triggering downstream operationsI want to retrieve deployment history and understand why an application is in a degraded state

Best for

Teams building observability-aware LLM agents for Kubernetes

DevOps engineers creating conversational deployment dashboards

Incident response workflows that need AI-assisted diagnosis of deployment issues

Requires

Argo CD 2.0+ with API access enabled

Read permissions on target applications in Argo CD RBAC

Network connectivity to Argo CD API endpoint

Limitations

Query latency depends on Argo CD server responsiveness; no client-side caching of application state

Resource tree queries can be expensive for large applications with hundreds of resources

No filtering or aggregation at the MCP layer; all filtering must happen in the LLM or client

What makes it unique

Exposes Argo CD's full application state graph (including resource trees, sync status, and health metrics) as queryable MCP resources, enabling LLMs to reason about deployment topology and health without requiring separate monitoring tools

vs alternatives

More comprehensive than kubectl-based queries because it provides Argo CD's high-level sync and health abstractions, whereas raw kubectl requires parsing multiple resource types and understanding Kubernetes primitives

argo cd application creation and configuration management

Medium confidence

Enables LLM agents to create new Argo CD applications and modify existing application configurations through MCP tools that translate high-level deployment specifications into Argo CD Application CRD manifests. Handles repository source configuration, sync policy, destination cluster/namespace, and automated sync settings via structured API calls to Argo CD.

Solves for

I want an AI agent to create a new Argo CD application from a Git repository without manual YAML editingI need to update an application's sync policy or target revision programmaticallyI want to configure automated sync and self-healing for an application through conversational commands

Best for

Platform teams automating application onboarding workflows

DevOps engineers building self-service deployment interfaces powered by LLMs

GitOps adoption programs that need to reduce manual Application manifest creation

Requires

Argo CD 2.0+ with admin or application-create permissions

Valid Git repository credentials configured in Argo CD

Target Kubernetes cluster registered in Argo CD

Limitations

No validation of Git repository accessibility or branch existence before creating application

Cannot manage complex Argo CD features like ApplicationSets, Kustomize overlays, or Helm value overrides through basic tool interface

Requires write permissions to Argo CD; no role-based access control enforcement at MCP layer

What makes it unique

Abstracts Argo CD Application CRD creation into natural language-driven MCP tools, allowing LLMs to reason about deployment configuration without requiring knowledge of Kubernetes manifest syntax or Argo CD's schema

vs alternatives

Simpler than manual Helm/Kustomize templating because it provides opinionated defaults and validation, whereas raw kubectl apply requires users to construct valid YAML and understand Argo CD's reconciliation model

argo cd repository and credential management

Medium confidence

Provides MCP tools to register Git repositories and manage credentials in Argo CD, translating repository configuration requests into Argo CD Repository CRD operations. Handles SSH key, HTTPS token, and OAuth credential types, enabling agents to configure repository access without exposing secrets in prompts or logs.

Solves for

I want to register a new Git repository with Argo CD so applications can pull from itI need to update repository credentials when a token expires or access changesI want to validate that a repository is accessible before creating applications that depend on it

Best for

Multi-tenant Argo CD deployments requiring dynamic repository registration

Platform teams automating repository onboarding for new teams or projects

Organizations managing credentials programmatically without manual Argo CD UI access

Requires

Argo CD 2.0+ with admin permissions

Valid Git credentials (SSH key, HTTPS token, or OAuth token)

Network access from Argo CD to Git repository

Limitations

Secrets are stored in Argo CD's encrypted secret store; no audit trail of credential changes at MCP layer

Cannot validate repository accessibility without attempting a connection, which may fail silently

No support for repository-level RBAC; all repositories are accessible to all applications once registered

What makes it unique

Abstracts Argo CD's Repository CRD and credential encryption into MCP tools, allowing agents to manage Git access without exposing secrets in LLM context or requiring manual Argo CD UI operations

vs alternatives

More secure than passing credentials through LLM prompts because it leverages Argo CD's built-in secret encryption, whereas direct API clients would require credential handling in application code

argo cd cluster registration and management

Medium confidence

Implements MCP tools to register Kubernetes clusters with Argo CD and manage cluster-level configuration, including cluster credentials, server URLs, and cluster-scoped settings. Translates cluster registration requests into Argo CD Cluster CRD operations with validation of cluster connectivity and RBAC permissions.

Solves for

I want to register a new Kubernetes cluster with Argo CD so applications can be deployed to itI need to update cluster credentials or server URL when infrastructure changesI want to validate that a cluster is reachable and has proper permissions before deploying applications

Best for

Multi-cluster Argo CD deployments requiring dynamic cluster registration

Platform teams automating cluster onboarding for new environments

Organizations managing cluster lifecycle programmatically

Requires

Argo CD 2.0+ with admin permissions

Valid kubeconfig for target Kubernetes cluster

Network access from Argo CD to cluster API server

Limitations

Cluster registration requires valid kubeconfig; no support for dynamic credential providers (e.g., cloud IAM)

Cannot validate cluster RBAC permissions without attempting operations; validation is best-effort

Cluster credentials are stored in Argo CD secrets; no audit trail of credential changes at MCP layer

What makes it unique

Exposes Argo CD's cluster registration and validation as MCP tools, enabling agents to manage multi-cluster deployments without requiring direct kubectl access or manual Argo CD UI operations

vs alternatives

Simpler than managing kubeconfig files directly because it provides Argo CD's cluster validation and credential encryption, whereas raw kubectl requires managing credentials across multiple contexts

argo cd notification and event streaming

Medium confidence

Provides MCP resource subscriptions or polling mechanisms to stream Argo CD application events (sync, health, error events) to LLM agents in real-time or near-real-time. Translates Argo CD's event stream into structured notifications that agents can consume for reactive workflows, such as triggering rollbacks or escalations on deployment failures.

Solves for

I want my AI agent to react immediately when an application sync fails or becomes unhealthyI need to stream deployment events to an LLM-based incident response systemI want to trigger automated remediation workflows when Argo CD detects deployment issues

Best for

Teams building reactive LLM agents that respond to deployment events

Incident response automation that needs real-time visibility into Argo CD state changes

Organizations implementing GitOps-driven self-healing workflows

Requires

Argo CD 2.0+ with event API enabled

MCP server with polling or WebSocket support

Network access to Argo CD API endpoint

Limitations

MCP does not natively support server-push notifications; event streaming requires polling or WebSocket extensions

Event history is limited to Argo CD's retention policy; cannot retrieve historical events beyond retention window

No filtering at the MCP layer; agents must process all events and filter in application logic

What makes it unique

Bridges Argo CD's event stream with LLM agent workflows through MCP, enabling agents to react to deployment state changes without requiring external event brokers or webhook integrations

vs alternatives

More integrated than webhook-based notifications because it leverages MCP's resource subscription model, whereas webhooks require separate infrastructure and credential management

argo cd rollback and deployment history management

Medium confidence

Exposes MCP tools to rollback applications to previous revisions and query deployment history, including previous sync operations, revisions, and deployment artifacts. Implements revision selection logic and rollback validation to ensure safe rollbacks without manual intervention or Argo CD UI access.

Solves for

I want to rollback an application to a previous revision when a deployment causes issuesI need to query deployment history to understand what changed between revisionsI want an AI agent to automatically rollback failed deployments based on health metrics

Best for

Teams implementing automated incident response with AI-assisted rollback decisions

DevOps engineers building self-healing deployment systems

Organizations requiring audit trails of deployment changes and rollbacks

Requires

Argo CD 2.0+ with sync history enabled

Write permissions to target application

Network access to Argo CD API endpoint

Limitations

Rollback is limited to Argo CD's sync history; cannot rollback to arbitrary Git commits without manual Git operations

No automatic validation that rollback target is stable; agents must check health status independently

Rollback operations are asynchronous; completion status requires polling or callback patterns

What makes it unique

Provides LLM agents with safe rollback capabilities through MCP, including revision history and validation, enabling automated incident response without requiring manual Argo CD UI or Git operations

vs alternatives

Safer than manual Git reverts because it leverages Argo CD's sync history and validation, whereas direct Git operations require understanding commit history and risk deploying unvalidated revisions

argo cd project and rbac policy management

Medium confidence

Implements MCP tools to create and manage Argo CD Projects, which enforce namespace, cluster, and repository restrictions for applications. Enables agents to define RBAC policies and project-level access controls, translating high-level policy intent into Argo CD AppProject CRD operations with validation of policy constraints.

Solves for

I want to create an Argo CD project that restricts applications to specific namespaces and clustersI need to enforce repository access policies so teams can only deploy from approved Git repositoriesI want to define role-based access controls for Argo CD applications without manual YAML editing

Best for

Multi-tenant Argo CD deployments requiring namespace and cluster isolation

Platform teams implementing self-service application deployment with guardrails

Organizations enforcing compliance policies through Argo CD RBAC

Requires

Argo CD 2.0+ with admin permissions

Understanding of Argo CD project constraints (namespaces, clusters, repositories)

Network access to Argo CD API endpoint

Limitations

Project-level RBAC is enforced at application creation time; cannot retroactively restrict existing applications

No support for dynamic policy evaluation; policies are static once defined

Policy validation is limited to syntax checking; semantic validation (e.g., cluster existence) is not performed

What makes it unique

Abstracts Argo CD's project-level access control into MCP tools, enabling agents to enforce deployment policies without requiring knowledge of Argo CD's RBAC model or manual manifest editing

vs alternatives

More granular than Kubernetes RBAC alone because it provides application-level policy enforcement, whereas raw Kubernetes RBAC requires managing multiple role bindings across namespaces

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with argocd-mcp, ranked by overlap. Discovered automatically through the match graph.

Workflow39

Argo Workflows

Kubernetes-native workflow engine.

multi-backend artifact storage and retrieval with automatic stagingweb ui and rest/grpc api for workflow management and monitoringclient sdk support for programmatic workflow submission and monitoring

3 shared capabilities

MCP Server28

Algorand

** - A comprehensive MCP server for tooling interactions(40+) and resource accessibility(60+) plus many useful prompts to interact with Algorand Blockchain.

algorand asset and application metadata resolutionalgorand smart contract interaction and state managementalgorand account state and balance querying

3 shared capabilities

MCP Server38

@ag-ui/mcp-apps-middleware

MCP Apps middleware for AG-UI that enables UI-enabled tools from MCP (Model Context Protocol) servers.

mcp server connection pooling and lifecycle managementmcp server capability discovery and tool registry

2 shared capabilities

MCP Server44

nacos

an easy-to-use dynamic service discovery, configuration and service management platform for building AI cloud native applications.

centralized-dynamic-configuration-management

1 shared capability

Repository27

MBro

** - A powerful interactive terminal **M**CP **Bro**wser client with tab completion and automatic documentation that allows you to work with multiple MCP servers, manage tools, and create complex workflows using AI assistants.

dynamic configuration reloading with watchdog-based file monitoring

1 shared capability

MCP Server27

🧲 Magg 🧲

** - A meta-MCP server that acts as a universal hub, allowing LLMs to autonomously discover, install, and orchestrate multiple MCP servers - essentially giving AI assistants the power to extend their own capabilities on-demand.

dynamic configuration hot-reloading with watchdog file monitoring

1 shared capability

Best For

✓DevOps teams building AI-assisted deployment orchestration
✓Platform engineers integrating Argo CD into LLM agent workflows
✓Organizations automating GitOps operations through conversational interfaces
✓Teams building observability-aware LLM agents for Kubernetes
✓DevOps engineers creating conversational deployment dashboards
✓Incident response workflows that need AI-assisted diagnosis of deployment issues
✓Platform teams automating application onboarding workflows
✓DevOps engineers building self-service deployment interfaces powered by LLMs

Known Limitations

⚠Requires network connectivity to Argo CD server; no local caching of application state
⚠Sync operations are asynchronous but MCP tool responses are synchronous, requiring polling or callback patterns for completion status
⚠No built-in retry logic or exponential backoff for failed sync operations
⚠Limited to Argo CD's native sync strategies; cannot implement custom deployment logic
⚠Query latency depends on Argo CD server responsiveness; no client-side caching of application state
⚠Resource tree queries can be expensive for large applications with hundreds of resources

Requirements

Argo CD 2.0+ server instance with gRPC or REST API enabledValid Argo CD authentication token or credentialsNetwork access from MCP server to Argo CD API endpointNode.js 16+ runtime for MCP serverArgo CD 2.0+ with API access enabledRead permissions on target applications in Argo CD RBACNetwork connectivity to Argo CD API endpointMCP server with Argo CD client library

Input / Output

Accepts: application name (string), sync strategy (enum: sync, refresh, hard-refresh), revision/branch specification (optional string), namespace filter (optional string), resource type filter (optional string), repository URL (string), target path in repo (string), destination cluster (string), destination namespace (string), sync policy (enum: automatic, manual), revision/branch (string, default: HEAD), credential type (enum: ssh, https, oauth), credential value (string, secret), insecure flag (boolean, for self-signed certificates), cluster name (string), cluster server URL (string), kubeconfig (string or file), cluster labels (optional object), application name filter (optional string), event type filter (optional enum: sync, health, error), polling interval (optional number, in seconds), target revision (string, optional; defaults to previous revision), rollback reason (string, optional, for audit), project name (string), allowed namespaces (array of strings), allowed clusters (array of strings), allowed repositories (array of strings), role definitions (optional array of role objects)

Produces: sync operation status (JSON with operationState, syncResult), application health status (Healthy, Progressing, Degraded), deployment timestamp and revision information, application manifest (YAML/JSON), sync status object (synced, out-of-sync, unknown), health status (Healthy, Progressing, Degraded, Unknown), resource tree (hierarchical JSON of deployed resources), operation history (array of sync operations with timestamps), created Application manifest (YAML/JSON), application status (Created, Pending, Error), validation errors (if creation failed), repository registration status (Success, Failed), connection test result (Reachable, Unreachable), error messages (if registration failed), cluster registration status (Success, Failed), cluster connectivity test result (Reachable, Unreachable), RBAC validation result (Authorized, Unauthorized), event stream (array of event objects), event metadata (timestamp, application, event type, status), event details (error messages, sync results, health status), rollback operation status (Initiated, Succeeded, Failed), deployment history (array of previous sync operations), revision details (Git commit, timestamp, author), health status after rollback, project creation status (Success, Failed), project manifest (YAML/JSON)

UnfragileRank

Adoption47%(25% weight)

Quality17%(25% weight)

Ecosystem50%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit argocd-mcp→

Package Details

npm

Registry

0.5.0

Version

10,595

Weekly Downloads

About

Argo CD MCP Server

Alternatives to argocd-mcp

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of argocd-mcp?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities8 decomposed

argo cd application state synchronization via mcp

Medium confidence

Solves for

Best for

DevOps teams building AI-assisted deployment orchestration

Platform engineers integrating Argo CD into LLM agent workflows

Organizations automating GitOps operations through conversational interfaces

Requires

Argo CD 2.0+ server instance with gRPC or REST API enabled

Valid Argo CD authentication token or credentials

Network access from MCP server to Argo CD API endpoint

Limitations

Requires network connectivity to Argo CD server; no local caching of application state

Sync operations are asynchronous but MCP tool responses are synchronous, requiring polling or callback patterns for completion status

No built-in retry logic or exponential backoff for failed sync operations

What makes it unique

vs alternatives

Provides native MCP integration for Argo CD workflows, whereas alternatives typically require custom REST API clients or kubectl plugins that lack semantic understanding of deployment intent

argo cd application state querying and monitoring

Medium confidence

Solves for

Best for

Teams building observability-aware LLM agents for Kubernetes

DevOps engineers creating conversational deployment dashboards

Incident response workflows that need AI-assisted diagnosis of deployment issues

Requires

Argo CD 2.0+ with API access enabled

Read permissions on target applications in Argo CD RBAC

Network connectivity to Argo CD API endpoint

Limitations

Query latency depends on Argo CD server responsiveness; no client-side caching of application state

Resource tree queries can be expensive for large applications with hundreds of resources

No filtering or aggregation at the MCP layer; all filtering must happen in the LLM or client

What makes it unique

vs alternatives

argo cd application creation and configuration management

Medium confidence

Solves for

Best for

Platform teams automating application onboarding workflows

DevOps engineers building self-service deployment interfaces powered by LLMs

GitOps adoption programs that need to reduce manual Application manifest creation

Requires

Argo CD 2.0+ with admin or application-create permissions

Valid Git repository credentials configured in Argo CD

Target Kubernetes cluster registered in Argo CD

Limitations

No validation of Git repository accessibility or branch existence before creating application

Cannot manage complex Argo CD features like ApplicationSets, Kustomize overlays, or Helm value overrides through basic tool interface

Requires write permissions to Argo CD; no role-based access control enforcement at MCP layer

What makes it unique

vs alternatives

argo cd repository and credential management

Medium confidence

Solves for

Best for

Multi-tenant Argo CD deployments requiring dynamic repository registration

Platform teams automating repository onboarding for new teams or projects

Organizations managing credentials programmatically without manual Argo CD UI access

Requires

Argo CD 2.0+ with admin permissions

Valid Git credentials (SSH key, HTTPS token, or OAuth token)

Network access from Argo CD to Git repository

Limitations

Secrets are stored in Argo CD's encrypted secret store; no audit trail of credential changes at MCP layer

Cannot validate repository accessibility without attempting a connection, which may fail silently

No support for repository-level RBAC; all repositories are accessible to all applications once registered

What makes it unique

Abstracts Argo CD's Repository CRD and credential encryption into MCP tools, allowing agents to manage Git access without exposing secrets in LLM context or requiring manual Argo CD UI operations

vs alternatives

More secure than passing credentials through LLM prompts because it leverages Argo CD's built-in secret encryption, whereas direct API clients would require credential handling in application code

argo cd cluster registration and management

Medium confidence

Solves for

Best for

Multi-cluster Argo CD deployments requiring dynamic cluster registration

Platform teams automating cluster onboarding for new environments

Organizations managing cluster lifecycle programmatically

Requires

Argo CD 2.0+ with admin permissions

Valid kubeconfig for target Kubernetes cluster

Network access from Argo CD to cluster API server

Limitations

Cluster registration requires valid kubeconfig; no support for dynamic credential providers (e.g., cloud IAM)

Cannot validate cluster RBAC permissions without attempting operations; validation is best-effort

Cluster credentials are stored in Argo CD secrets; no audit trail of credential changes at MCP layer

What makes it unique

Exposes Argo CD's cluster registration and validation as MCP tools, enabling agents to manage multi-cluster deployments without requiring direct kubectl access or manual Argo CD UI operations

vs alternatives

Simpler than managing kubeconfig files directly because it provides Argo CD's cluster validation and credential encryption, whereas raw kubectl requires managing credentials across multiple contexts

argo cd notification and event streaming

Medium confidence

Solves for

Best for

Teams building reactive LLM agents that respond to deployment events

Incident response automation that needs real-time visibility into Argo CD state changes

Organizations implementing GitOps-driven self-healing workflows

Requires

Argo CD 2.0+ with event API enabled

MCP server with polling or WebSocket support

Network access to Argo CD API endpoint

Limitations

MCP does not natively support server-push notifications; event streaming requires polling or WebSocket extensions

Event history is limited to Argo CD's retention policy; cannot retrieve historical events beyond retention window

No filtering at the MCP layer; agents must process all events and filter in application logic

What makes it unique

Bridges Argo CD's event stream with LLM agent workflows through MCP, enabling agents to react to deployment state changes without requiring external event brokers or webhook integrations

vs alternatives

More integrated than webhook-based notifications because it leverages MCP's resource subscription model, whereas webhooks require separate infrastructure and credential management

argo cd rollback and deployment history management

Medium confidence

Solves for

Best for

Teams implementing automated incident response with AI-assisted rollback decisions

DevOps engineers building self-healing deployment systems

Organizations requiring audit trails of deployment changes and rollbacks

Requires

Argo CD 2.0+ with sync history enabled

Write permissions to target application

Network access to Argo CD API endpoint

Limitations

Rollback is limited to Argo CD's sync history; cannot rollback to arbitrary Git commits without manual Git operations

No automatic validation that rollback target is stable; agents must check health status independently

Rollback operations are asynchronous; completion status requires polling or callback patterns

What makes it unique

Provides LLM agents with safe rollback capabilities through MCP, including revision history and validation, enabling automated incident response without requiring manual Argo CD UI or Git operations

vs alternatives

Safer than manual Git reverts because it leverages Argo CD's sync history and validation, whereas direct Git operations require understanding commit history and risk deploying unvalidated revisions

argo cd project and rbac policy management

Medium confidence

Solves for

Best for

Multi-tenant Argo CD deployments requiring namespace and cluster isolation

Platform teams implementing self-service application deployment with guardrails

Organizations enforcing compliance policies through Argo CD RBAC

Requires

Argo CD 2.0+ with admin permissions

Understanding of Argo CD project constraints (namespaces, clusters, repositories)

Network access to Argo CD API endpoint

Limitations

Project-level RBAC is enforced at application creation time; cannot retroactively restrict existing applications

No support for dynamic policy evaluation; policies are static once defined

Policy validation is limited to syntax checking; semantic validation (e.g., cluster existence) is not performed

What makes it unique

Abstracts Argo CD's project-level access control into MCP tools, enabling agents to enforce deployment policies without requiring knowledge of Argo CD's RBAC model or manual manifest editing

vs alternatives

More granular than Kubernetes RBAC alone because it provides application-level policy enforcement, whereas raw Kubernetes RBAC requires managing multiple role bindings across namespaces

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to argocd-mcp

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

argocd-mcp

Capabilities8 decomposed

argo cd application state synchronization via mcp

argo cd application state querying and monitoring

argo cd application creation and configuration management

argo cd repository and credential management

argo cd cluster registration and management

argo cd notification and event streaming

argo cd rollback and deployment history management

argo cd project and rbac policy management

Related Artifactssharing capabilities

Argo Workflows

Algorand

@ag-ui/mcp-apps-middleware

nacos

MBro

🧲 Magg 🧲

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to argocd-mcp

Are you the builder of argocd-mcp?

Get the weekly brief

Data Sources

argocd-mcp

Capabilities8 decomposed

argo cd application state synchronization via mcp

argo cd application state querying and monitoring

argo cd application creation and configuration management

argo cd repository and credential management

argo cd cluster registration and management

argo cd notification and event streaming

argo cd rollback and deployment history management

argo cd project and rbac policy management

Related Artifactssharing capabilities

Argo Workflows

Algorand

@ag-ui/mcp-apps-middleware

nacos

MBro

🧲 Magg 🧲

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to argocd-mcp

Are you the builder of argocd-mcp?

Get the weekly brief

Data Sources