Aks MCP Server

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. The aks mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• cli_command — The complete Azure CLI command to execute (e.g., az aks list --resource-group myRG, az vm list --subscription )
• timeout — Optional timeout in seconds (default: 120)
• readonly — Only read operations are allowed
• Read — Only** (all access levels):
• show — Show cluster details
• list — List clusters in subscription/resource group
• get-versions — Get available Kubernetes versions
• check-network — Perform outbound network connectivity check
• nodepool-list — List node pools in cluster
• nodepool-show — Show node pool details
• account-list — List Azure subscriptions
• create — Create new cluster

Configuration

You will need 8 environment variables: AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, CLIENT_ID, CLIENT_SECRET, TENANT_ID, AZURE_SUBSCRIPTION_ID, SUBSCRIPTION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

1. Set up Azure CLI and authenticate:

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Aks MCP's toolset — cli_command, timeout, readonly and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Azure; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aks MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Aks MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aks mcp mcp server does with a few real requests.