AKS-MCP 是一款模型上下文协议（MCP）服务器，支持人工智能助手 与Azure Kubernetes Service（AKS）集互。它作为桥梁 在AI工具（如GitHub Copilot、Claude及其他兼容MCP的AI）之间 助手）和AKS，将自然语言请求转换为AKS操作 并以AI工具能理解的形式返回结果。

它允许人工智能工具：

• 操作（CRUD）AKS资源
• 检索与 AKS 集群相关的详细信息（VNet、子网、NSG、路由表等）
• 管理多集群场景下的Azure舰队运营

支持的部署模型与安全考虑

AKS-MCP设计为由单一受信任用户本地运行，作为桥接器运行 在该用户自己的AI助手和他们自己的Azure/AKS资源之间。 是该项目唯一支持并加固的部署模式。

信任界限

AKS-MCP 执行命令行工具——包括 az、kubectl、helm。 [cilium，以及hubble — 利用它运行的进程的身份。它 不执行每个呼叫者授权，也不尝试沙箱 它运行的命令。因此：

AKS-MCP

The AKS-MCP is a Model Context Protocol (MCP) server that enables AI assistants to interact with Azure Kubernetes Service (AKS) clusters. It serves as a bridge between AI tools (like GitHub Copilot, Claude, and other MCP-compatible AI assistants) and AKS, translating natural language requests into AKS operations and returning the results in a format the AI tools can understand.

It allows AI tools to:

• Operate (CRUD) AKS resources
• Retrieve details related to AKS clusters (VNets, Subnets, NSGs, Route Tables, etc.)
• Manage Azure Fleet operations for multi-cluster scenarios

Supported Deployment Model and Security Considerations

AKS-MCP is designed to be run locally, by a single trusted user, as a bridge between that user’s own AI assistant and their own Azure/AKS resources. This is the only deployment model the project supports and hardens for.

The trust boundary

AKS-MCP executes command-line tools — including az, kubectl, helm, cilium, and hubble — using the identity of the process it runs as. It does not perform per-caller authorization, and it does not attempt to sandbox the commands it runs. Therefore:

Anyone who can invoke AKS-MCP tools effectively has the full Azure and Kubernetes privileges of the identity AKS-MCP is running under.

This includes the ability to obtain reusable credentials. For example, in readwrite or admin mode a caller can reach Azure Resource Manager and AKS with the server identity’s full authority, and kubectl or helm can be used to read Secrets, mint service account tokens, or deploy arbitrary workloads into the cluster. This is an inherent consequence of exposing a CLI execution surface — it is not prevented by --access-level.

Specific credential-returning Azure CLI commands (such as az account get-access-token and az aks get-credentials) are rejected by an explicit denylist. That denylist reduces accidental exposure — it is not a security boundary, it does not cover the kubectl, helm, cilium, or hubble surfaces, and it must not be relied upon to contain an untrusted caller.

Treat the ability to call AKS-MCP as equivalent to handing over a shell that is already logged in as the server identity.

Network exposure and local authority

Removing HTTP/SSE transports and the official remote deployment artifacts removes the supported network-reachable service and its remote-caller threat model. In the supported configuration, AKS-MCP has no listener that accepts requests from the network.

This does not make the local MCP client, its prompts, or --access-level an authorization boundary. A person or process that controls the local client, its server configuration, or AKS-MCP can normally run the same CLI commands under the same identity without AKS-MCP. Protecting the workstation, client