Your organization wants agents to automatically discover approved MCP servers without requiring each developer to manually configure server endpoints in their agent definition files. What feature should you configure to enable centralized MCP server discovery?
Select an answer to reveal the explanation.
Short Explanation
You should configure an MCP registry because it acts like a central catalog of approved servers. Agents can query the registry to discover servers and connection details without developers hard-coding endpoints.
Full Explanation
MCP registries solve the scalability problem of managing tool discovery across many agents and developers. Rather than each agent definition file manually listing every MCP server endpoint, a registry provides a centralized catalog that can be queried programmatically. The registry exposes a list of available MCP servers including their names, descriptions, transport details, and connection URLs. Agent runtimes or developer tools can be configured with a registry URL and will automatically surface available servers for selection.
The option proposing a .github/mcp-servers.json file in each repository is incorrect because while GitHub does read certain well-known files from repositories, such as CODEOWNERS or workflow files, there is no standard .github/mcp-servers.json discovery mechanism built into Copilot. Each agent's tool configuration still needs explicit definition.
Configuring an MCP registry that points to a catalog of approved servers is correct. MCP registries are the purpose-built mechanism for centralized server discovery. Organizations can host their own registry or use public ones, such as those from GitHub or third-party providers. Once the registry URL is configured in the Copilot settings or agent runtime, developers and agents can browse or auto-load available servers from the catalog.
The option proposing an auto-tool-discovery flag in GitHub organization settings is incorrect. There is no such flag that scans all installed GitHub Apps and registers their APIs as MCP tools. GitHub Apps and MCP servers are distinct integration surfaces.
The option proposing publishing each MCP server as a GitHub Package under the organization namespace is incorrect. GitHub Packages is a package registry for artifacts like npm modules, container images, and Maven artifacts. While an MCP server could be distributed as an npm package via GitHub Packages, the Packages API does not auto-register them as agent tools. Discovery via Packages would require manual lookup and configuration.
The key exam point: MCP registries are the centralized discovery catalog. Allow lists are a different feature and control what tools from a discovered server are permitted. Both work together but solve different problems.