Missing MCP manifest for GitHub Copilot registry integration

[BartoszKawa]

Hi,

According to the official GitHub Copilot tutorial on configuring MCP server access, each MCP server needs to expose a manifest JSON (via a manifest_url) that describes the server’s capabilities, tools, and schema.

We’re currently trying to register Azure DevOps MCP in a Copilot MCP registry and configure access for our organization. However, this package (@azure-devops/mcp) doesn’t appear to include or publish a manifest file — neither in the GitHub repository nor in the npm package metadata.

#Why this matters:
The GitHub Copilot MCP registry requires a valid manifest_url for every MCP server entry. Without an accessible manifest, Copilot cannot validate or register this MCP for managed access.

#Questions:

1. Is there an official manifest file (static or generated) available for @azure-devops/mcp?
2. If not yet published, do you plan to provide one for registry integration?
3. Or should we generate and host a manifest ourselves (based on available documentation and tools)?

Thanks in advance for clarifying!

[danhellem]

see #637. Closing this discussion