MCP Integration Reference

Loaded when troubleshooting MCP tool calls, debugging the fallback chain, or understanding the API response format.

---

Tool Discovery

Always call mcp_azure_mcp_aks first to discover the current available tool surface. Do not assume a fixed action name — the available actions depend on the MCP server version deployed to the client.

mcp_azure_mcp_aks({ action: "discover" })

The response lists available actions and their parameter schemas. Use the returned schema — do not hardcode parameter names.

---

Assessment Call

After calling discover, use the assessment action name returned in the response. Pass parameters according to the discovered schema — do not hardcode action names or API versions.

Typical parameters include:

• subscriptionId — Azure subscription ID
• resourceGroupName — resource group containing the cluster
• resourceName — AKS cluster name
• scope (optional) — filter by namespaces or workload types

Example shape (use actual action name and schema from discover output):

mcp_azure_mcp_aks({