Add support for an MCP server package type that resolves to a local executable

Describe the feature or problem you'd like to solve

When using an MCP registry that includes an MCP server pointing to a local exe, there is no way to have Copilot install it correctly. Only npm, pypi, oci and docker are supported as "registry type"

Proposed solution

We have MCP servers served as simple binaries. Those are documented in our MCP registry (configured in Azure API Center and enforced through GitHub Copilot Enterprise).

To be able to install those MCP servers using copilot (eg /mcp search ...) correctly, copilot should support a new "registryType" in addition to the existing ones (npm, pypi, oci, docker).

This could be something like "none" or "executable", etc.

The expected behavior would be that if the MCP registry lists an MCP server with the new registry type (none, executable, etc), copilot would add the MCP server in mcp-config.json, fully respecting the MCP registry definition and thus pointing to the executable and NOT using npx, uvx, etc as it currently does.

For reference, here's the analysis of the problematic part of copilot's codebase:

Analyzed the CLI's bundled  app.js . Found the exact logic (functions  umi / cmi  in the MCP-registry install module):

Root cause: Copilot CLI's registry→launch-config converter only supports 4 hardcoded  registryType s, each mapped to a fixed launcher — there's no "binary/exe" package type at all:

switch (t.registryType) {
  case "npm":    n.push("npx"), ..., n.push("-y"), n.push(identifier[@version]); break;
  case "pypi":   n.push("uvx"), ..., n.push(identifier); break;
  case "oci":
  case "docker": n.push("docker","run","--rm","-i"), ...; break;
  default: throw new Error(`Unsupported package type: ${t.registryType}`);
}

And a supportability gate:  ["npm","pypi","oci","docker"].includes(registryType)  — anything else is rejected as "not yet supported."

What this means for you: if your registry's GitLab MCP entry has  registryType: "npm" , Copilot always synthesizes  npx -y <identifier>@<version>  — it never reads or honors a custom "command/exe path" field from the registry package object, regardless of what your registry intends. There's a separate  commandToRegistryType  map (npx→npm, uvx→pypi, dotnet→nuget, docker→docker, brew→homebrew, mcpb→mcpb) used for fingerprinting, but the actual launch-builder ( umi ) doesn't implement nuget/homebrew/mcpb either — only npm/pypi/oci/docker.

Bottom line: there's currently no supported registry package type that resolves to a raw local executable path. To point at your exe you'd need to bypass  /mcp search / /mcp add -from-registry and instead manually add the server ( /mcp add  with explicit command, or edit the MCP config file directly) with  command: "C:\path\to\gitlab-mcp.exe" 

Example prompts or workflows

No response

Additional context

No response

Commencez dans l’app.js incluse, au niveau des fonctions d’installation de MCP-registry umi et cmi, notamment la vérification de prise en charge de registryType et le changement de commande de lancement. Suivez la manière dont les points d’entrée /mcp search et /mcp add-from-registry produisent mcp-config.json. Le travail est terminé lorsqu’un type de registry exécutable documenté est accepté et que la configuration obtenue pointe directement vers l’exécutable local du registry au lieu d’utiliser npx, uvx ou Docker.