aks-mcp and mcp-for-argocd
These are complements: AKS-MCP enables AI assistants to manage Kubernetes clusters directly, while MCP-for-ArgoCD enables AI assistants to manage GitOps deployments within those clusters, so both can be used together in a unified AI-driven workflow.
About aks-mcp
Azure/aks-mcp
A Model Context Protocol (MCP) server that enables AI assistants to interact with AKS clusters. It serves as a bridge between AI tools (like Claude, Cursor, and GitHub Copilot) and AKS.
Implements flexible Azure authentication (service principal, workload identity, managed identity) via Azure CLI, with role-based access control (readonly/readwrite/admin) to gate sensitive operations. Provides unified tools for Azure CLI operations, AKS cluster management, network resources, monitoring/diagnostics, and node-level log collection, supporting both modern and legacy tool interfaces for backward compatibility.
About mcp-for-argocd
argoproj-labs/mcp-for-argocd
An implementation of Model Context Protocol (MCP) server for Argo CD.
Exposes 15+ Argo CD management tools covering cluster operations, application lifecycle (create/update/sync/delete), and resource inspection including workload logs and event tracking. Uses stdio and HTTP stream transports with environment-based authentication, supporting direct integration into VS Code, Claude Desktop, and Cursor with optional read-only mode for restricted access.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work