Skip to content

Updated the MCP Registry validation steps by including name, description and version, as done in VS Code. #42331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
manupk wants to merge 3 commits into
base: main
Choose a base branch
from
+2 −2
Open

Updated the MCP Registry validation steps by including name, description and version, as done in VS Code. #42331

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a72f72e
Clarify MCP server validation steps in IDE.
manupk Jan 10, 2026
6f1f952
Enhance MCP allowlist enforcement limitations details
manupk Jan 10, 2026
4b1af4a
Changed to server name/ID to reflect better field.
manupk Jan 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...t/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ At its core, an MCP registry is a set of HTTPS endpoints that serve details abou
* Publish your own custom implementation.

> [!NOTE]
> If you want your developers to have access to local MCP servers, include those servers in your registry with the correct server ID. For more information, see [AUTOTITLE](/copilot/reference/mcp-allowlist-enforcement).
> If you want your developers to have access to local MCP servers, include those servers in your registry with the correct server name/ID, description and version. For more information, see [AUTOTITLE](/copilot/reference/mcp-allowlist-enforcement).
To create a valid MCP registry that is reachable by {% data variables.product.prodname_copilot %}, the registry must meet the following requirements:
* [Endpoint and specification requirements](#endpoint-and-specification-requirements)
Expand Down
2 changes: 1 addition & 1 deletion content/copilot/reference/mcp-allowlist-enforcement.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ contentType: reference

MCP allowlist enforcement currently has the following limitations:

* Enforcement is based only on server name/ID matching, which can be bypassed by editing configuration files
* Enforcement is based only on server name/ID, description and version matching, which can be bypassed by editing configuration files
* Strict enforcement that prevents installation of non-registry servers is not yet available

For the highest level of security, you can **disable MCP servers in {% data variables.product.prodname_copilot_short %}** until strict enforcement is available.
Expand Down
Loading