{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-argocd-mcp","slug":"npm-argocd-mcp","name":"argocd-mcp","type":"mcp","url":"https://www.npmjs.com/package/argocd-mcp","page_url":"https://unfragile.ai/npm-argocd-mcp","categories":["mcp-servers"],"tags":["mcp","argocd","argocd-mcp","argocd-mcp-server","argo-cd","argo-cd-mcp","argo-cd-mcp-server","cicd","cicd-mcp","cicd-mcp-server","gitops","gitops-mcp","gitops-mcp-server","kubernetes","kubernetes-mcp","kubernetes-mcp-server"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-argocd-mcp__cap_0","uri":"capability://tool.use.integration.argo.cd.application.state.synchronization.via.mcp","name":"argo cd application state synchronization via mcp","description":"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.","intents":["I want an AI agent to automatically sync my Argo CD applications when deployment conditions are met","I need to trigger application synchronization from an LLM-based deployment assistant without manual kubectl access","I 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"],"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"],"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","Node.js 16+ runtime for MCP server"],"input_types":["application name (string)","sync strategy (enum: sync, refresh, hard-refresh)","revision/branch specification (optional string)"],"output_types":["sync operation status (JSON with operationState, syncResult)","application health status (Healthy, Progressing, Degraded)","deployment timestamp and revision information"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_1","uri":"capability://search.retrieval.argo.cd.application.state.querying.and.monitoring","name":"argo cd application state querying and monitoring","description":"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.","intents":["I want to ask an AI agent about the current deployment status of my applications without logging into Argo CD UI","I need to check if an application is healthy and synced before triggering downstream operations","I 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"],"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","Historical data is limited to Argo CD's retention policy (default 24 hours for operation history)"],"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","MCP server with Argo CD client library"],"input_types":["application name (string)","namespace filter (optional string)","resource type filter (optional string)"],"output_types":["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)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_2","uri":"capability://tool.use.integration.argo.cd.application.creation.and.configuration.management","name":"argo cd application creation and configuration management","description":"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.","intents":["I want an AI agent to create a new Argo CD application from a Git repository without manual YAML editing","I need to update an application's sync policy or target revision programmatically","I 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"],"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","No rollback capability if application creation succeeds but subsequent configuration fails"],"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","Network access to Argo CD API endpoint"],"input_types":["application name (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)"],"output_types":["created Application manifest (YAML/JSON)","application status (Created, Pending, Error)","validation errors (if creation failed)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_3","uri":"capability://tool.use.integration.argo.cd.repository.and.credential.management","name":"argo cd repository and credential management","description":"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.","intents":["I want to register a new Git repository with Argo CD so applications can pull from it","I need to update repository credentials when a token expires or access changes","I 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"],"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","Credential rotation requires manual updates; no automatic token refresh mechanism"],"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","Argo CD secret encryption configured"],"input_types":["repository URL (string)","credential type (enum: ssh, https, oauth)","credential value (string, secret)","insecure flag (boolean, for self-signed certificates)"],"output_types":["repository registration status (Success, Failed)","connection test result (Reachable, Unreachable)","error messages (if registration failed)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_4","uri":"capability://tool.use.integration.argo.cd.cluster.registration.and.management","name":"argo cd cluster registration and management","description":"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.","intents":["I want to register a new Kubernetes cluster with Argo CD so applications can be deployed to it","I need to update cluster credentials or server URL when infrastructure changes","I 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"],"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","No support for cluster-level network policies or firewall rules; assumes network connectivity exists"],"requires":["Argo CD 2.0+ with admin permissions","Valid kubeconfig for target Kubernetes cluster","Network access from Argo CD to cluster API server","Argo CD service account with cluster-admin or equivalent permissions"],"input_types":["cluster name (string)","cluster server URL (string)","kubeconfig (string or file)","cluster labels (optional object)"],"output_types":["cluster registration status (Success, Failed)","cluster connectivity test result (Reachable, Unreachable)","RBAC validation result (Authorized, Unauthorized)","error messages (if registration failed)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_5","uri":"capability://search.retrieval.argo.cd.notification.and.event.streaming","name":"argo cd notification and event streaming","description":"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.","intents":["I want my AI agent to react immediately when an application sync fails or becomes unhealthy","I need to stream deployment events to an LLM-based incident response system","I 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"],"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","Polling-based implementation adds latency (typically 5-30 seconds) compared to true event streaming"],"requires":["Argo CD 2.0+ with event API enabled","MCP server with polling or WebSocket support","Network access to Argo CD API endpoint","Sufficient API rate limits for polling frequency"],"input_types":["application name filter (optional string)","event type filter (optional enum: sync, health, error)","polling interval (optional number, in seconds)"],"output_types":["event stream (array of event objects)","event metadata (timestamp, application, event type, status)","event details (error messages, sync results, health status)"],"categories":["search-retrieval","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_6","uri":"capability://tool.use.integration.argo.cd.rollback.and.deployment.history.management","name":"argo cd rollback and deployment history management","description":"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.","intents":["I want to rollback an application to a previous revision when a deployment causes issues","I need to query deployment history to understand what changed between revisions","I 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"],"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","History retention is limited to Argo CD's operation history window (default 24 hours)"],"requires":["Argo CD 2.0+ with sync history enabled","Write permissions to target application","Network access to Argo CD API endpoint"],"input_types":["application name (string)","target revision (string, optional; defaults to previous revision)","rollback reason (string, optional, for audit)"],"output_types":["rollback operation status (Initiated, Succeeded, Failed)","deployment history (array of previous sync operations)","revision details (Git commit, timestamp, author)","health status after rollback"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-argocd-mcp__cap_7","uri":"capability://tool.use.integration.argo.cd.project.and.rbac.policy.management","name":"argo cd project and rbac policy management","description":"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.","intents":["I want to create an Argo CD project that restricts applications to specific namespaces and clusters","I need to enforce repository access policies so teams can only deploy from approved Git repositories","I 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"],"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","No audit trail of policy changes at MCP layer; changes are logged in Argo CD but not exposed through MCP"],"requires":["Argo CD 2.0+ with admin permissions","Understanding of Argo CD project constraints (namespaces, clusters, repositories)","Network access to Argo CD API endpoint"],"input_types":["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)"],"output_types":["project creation status (Success, Failed)","project manifest (YAML/JSON)","validation errors (if creation failed)"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["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","Node.js 16+ runtime for MCP server","Argo CD 2.0+ with API access enabled","Read permissions on target applications in Argo CD RBAC","Network connectivity to Argo CD API endpoint","MCP server with Argo CD client library","Argo CD 2.0+ with admin or application-create permissions","Valid Git repository credentials configured in Argo CD"],"failure_modes":["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","No filtering or aggregation at the MCP layer; all filtering must happen in the LLM or client","Historical data is limited to Argo CD's retention policy (default 24 hours for operation history)","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","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.26,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:35.215Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-argocd-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-argocd-mcp"}},"signature":"BFK7pRc5msZEUSG96W7jGC0A0C/+eGiO9KyQF5creMB0sZb80Qjo7fen1Dx6sv2LIbVe/Di97aUj9Z41OYWiDg==","signedAt":"2026-06-16T00:57:59.517Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-argocd-mcp","artifact":"https://unfragile.ai/npm-argocd-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-argocd-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}