Updating AKS MCP to v.0.0.17 and fixing WSL activation

[tejhan]

This PR updates our AKS MCP registration logic to use newly standardized vscode.McpServerDefinitionProvider, bump to the most recent v.0.0.17 version, and remedies failing installations on remote environments.

• Switched to registerMcpServerDefinitionProvider implemnetation, which runs on the extension host the user is in (which properly captures remote environemnts)
• Added contributes.mcpServerDefinitionProviders to package.json
• Bumped aks.aksmcpserver.releaseTag from v.0.0.16 -> v.0.0.17
• Added getEnabledComponentsArgs helper to pass the component with preservation of previous behavior

The registration now automatically occurs on activation, and further installation/starting the server will remain user invoked as it was before.

Resolves

• install MCP server inside WSL doesn't work #1974

[Copilot]

Pull request overview

This PR updates the AKS MCP server integration to use VS Code’s MCP server definition provider mechanism (to better support remote environments like WSL), and bumps the bundled AKS MCP server release tag to v0.0.17.

Changes:

• Register an aks-mcp MCP server definition provider during extension activation instead of writing mcp.servers directly.
• Remove the legacy “Setup AKS MCP Server” command and its quick action entry.
• Update the default aks.aksmcpserver.releaseTag from v0.0.16 to v0.0.17.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
src/extension.ts	Registers the AKS MCP server provider on activation and removes the legacy setup command registration.
src/commands/quickActions/aksQuickActions.ts	Removes the MCP setup command from quick actions and simplifies grouping logic accordingly.
src/commands/aksMCP/aksMCPServer.ts	Replaces “write to user settings” behavior with an MCP server definition provider that resolves the binary on demand.
package.json	Adds contributes.mcpServerDefinitionProviders, bumps MCP release tag default to v0.0.17, and removes the legacy setup command contribution.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[bosesuneha]

lgtm

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

src/commands/aksMCP/aksMCPServer.ts:25

• The provider doesn't expose an onDidChangeMcpServerDefinitions event, so changes to the aks.aksmcpserver.enabledComponents (or releaseTag) settings made after activation won't propagate to VS Code's MCP server list. Users will need to restart VS Code (or stop/start the server, since resolve recomputes args) for new component flags or a new release tag to take effect. Consider emitting that event when the relevant configuration sections change via vscode.workspace.onDidChangeConfiguration.

    const provider: vscode.McpServerDefinitionProvider<vscode.McpStdioServerDefinition> = {
        // Binary path left empty, resolveMcpServerDefinition sets it further below.
        provideMcpServerDefinitions: () => [
            new vscode.McpStdioServerDefinition("AKS MCP", "", ["--transport", "stdio", ...getEnabledComponentsArgs()]),
        ],
        // Downloads binary then points the server at it.
        resolveMcpServerDefinition: async (server) => {
            const binary = await getAKSMCPServerBinaryPath();
            if (failed(binary)) {
                throw new Error(`Failed to download AKS MCP server: ${binary.error}`);
            }
            server.command = binary.result;
            server.args = ["--transport", "stdio", ...getEnabledComponentsArgs()];
            return server;
        },
    };

[Copilot]

Pull request overview

Copilot reviewed 7 out of 10 changed files in this pull request and generated 1 comment.