v0.0.20

Breaking change: AKS-MCP is now stdio-only

AKS-MCP now supports only a local stdio subprocess launched by an MCP client. This release removes the network-reachable and remote-deployment model.

Removed

• SSE and streamable HTTP transports
• Browser-facing OAuth/OBO, token forwarding, and token-only authentication
• AKS RunCommand execution used by the removed token-only path
• Container-image distribution, Helm charts, Kubernetes deployment artifacts, and their publishing workflows

Migration

1. Download the binary for your platform from this release.
2. Configure your MCP client to start that binary as a local stdio subprocess.
3. Use the local user's Azure CLI and Kubernetes configuration (az login, kubeconfig, and required CLI tools).

Remote deployments cannot be upgraded in place. Move the MCP client configuration to a local binary installation instead. HTTP, SSE, container, Kubernetes, Helm, proxy, and gateway deployments are outside the project's supported security and support boundary.

See #394, #395, and #396 for details.

What's Changed

• Feat/ig cluster extension by Qasim Sarfraz (@mqasimsarfraz) in #389
• docs: clarify supported deployment model and security boundary by gossion in #393
• Make the MCP server stdio-only by gossion in #395
• Remove remote deployment and container distribution support by gossion in #396

Full Changelog: v0.0.19...v0.0.20