/mcp search constructs wrong URL for custom MCP registries — /v0.1/ segment is missing

[lvthillo]

Describe the bug

The /mcp search experimental command (added in 1.0.49) calls {registryUrl}/servers instead of {registryUrl}/v0.1/servers, producing a 404 against any registry whose URL doesn't already include /v0.1 in the path. This breaks the org-level "MCP Registry URL" setting for self-hosted MCP registries (e.g. Azure API Center), even though the same registry works correctly in VS Code's @mcp.

Affected version

GitHub Copilot CLI 1.0.49.

Steps to reproduce the behavior

1. Set the org-level "MCP Registry URL" to any registry whose base URL does not already include /v0.1/, e.g. an Azure API Center URL ending in /workspaces/default. e.g. https://xxx.data.<region>.azure-apicenter.ms/workspaces/default
2. Run /mcp search

Error:

Failed to load registry: RegistryError: Failed to list servers: Not Found

Expected behavior

mcp search should return the available / allowed MCP servers.

Additional context

When I update our url from https://xxx.data.<region>.azure-apicenter.ms/workspaces/defaultto https://xxx.data.<region>.azure-apicenter.ms/workspaces/default/v0.1/; then it works in Copilot CLI but the vscode integration breaks.

[almaleksia]

Thank you for the report!