Retrieve Argo CD version information for a specified connection.
MIT
751,414 tools. Updated 2026-11-06 14:41
"Kubernetes cluster management with Argo CD GitOps" matching MCP tools:
- Retrieve the Kubernetes resource tree for an Argo CD application, showing all created resources and their relationships.MIT
- Retrieve detailed information about a specific Argo CD cluster, including connection info and namespaces.MIT
- Retrieve configuration settings of an Argo CD instance by specifying the connection name.MIT
- Activate high-availability control plane on a managed Kubernetes cluster. Requires explicit confirmation due to added monthly cost and irreversibility.MIT
- Create a revocable kubeconfig credential for a managed Kubernetes cluster, enabling standing automation with admin or view access. Returns a bearer token embedded in YAML.MIT
Matching MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to inspect Argo CD applications, check sync and health status, list resources, review events, refresh applications, and optionally trigger sync operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Argo CD applications, managing clusters, applications, and resources through natural language.Apache 2.0
Matching MCP Connectors
MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2
Public ISO 3166-1 record for CD.
- Retrieve live Kubernetes deployment status for a cluster, including replica counts, pod health, and resource usage, to investigate deployment health or pod failures.MIT
- Uninstall a Helm release from a Kubernetes cluster, removing all associated resources. Specify cluster name, release name, and optional namespace.MIT
- Retrieve metadata for long-lived kubeconfig credentials (ServiceAccounts) of a managed Kubernetes cluster, including status and expiration. Use to list active credentials and obtain credential IDs for download.MIT
- Retrieves the kubeconfig YAML for a Kubernetes cluster so you can connect kubectl and other tooling. Requires the cluster ID and a read-write API key, since it grants cluster access.Apache 2.0
- Preview the cost of a Kubernetes cluster configuration before creation, using the same arguments as cluster creation.Apache 2.0
- Retrieve all node pools for a Kubernetes cluster to identify available compute resources and workloads. Use this to verify if a cluster can run workloads.Apache 2.0
- List available Kubernetes node packages and their sizing and pricing tiers before creating a cluster, with pagination to browse all options.Apache 2.0
- Retrieve a Kubernetes cluster by UUID to inspect its configuration and, with details=true, view node and status information. Use the ID from the cluster list.Apache 2.0
- Lists all namespaces in the connected Kubernetes cluster, returning an alphabetically sorted list with total count.MIT
- Check AMKO GSLB status by reading avi-system pods and any GSLBConfig YAML for multi-cluster Kubernetes questions; uses current kubectl context. Not for single-cluster AKO health.MIT
- Lists Kubernetes packages from Helm, CRDs, Argo, and Flux with versions, health, and source attribution. Answers what is installed and flags orphaned operators in a single call.Apache 2.0
- Upgrade a Tanzu Kubernetes cluster to a new Kubernetes version and poll cluster status until running. Use for K8s version changes, not node scaling.MIT
- Retrieve recent Kubernetes events from a managed cluster to identify why pods are unhealthy. Optionally filter by namespace and limit the number of events returned.Apache 2.0
- Check if a Kubernetes cluster is reachable and retrieve its nodes and namespaces before deployment to avoid misdiagnosing connection issues as deployment failures.MIT
- Identify root cause of a broken Kubernetes workload or GitOps reconciler by collecting resource details, logs, events, and startup blockers in one round-trip.Apache 2.0