From a72f72eca782fdabf5b991e638b182bd0bb988d2 Mon Sep 17 00:00:00 2001 From: Manu PK Date: Sat, 10 Jan 2026 22:04:38 +0530 Subject: [PATCH 1/3] Clarify MCP server validation steps in IDE. Updated instructions for including local MCP servers in the registry to specify correct name, description, and version. This is as per the validation done in VS Code. --- .../manage-mcp-usage/configure-mcp-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md b/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md index b4e4f8428580..a10a91404000 100644 --- a/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md +++ b/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md @@ -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 name, 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) From 6f1f95242320afa680bfa1cf6e91b8347f68da04 Mon Sep 17 00:00:00 2001 From: Manu PK Date: Sat, 10 Jan 2026 22:06:50 +0530 Subject: [PATCH 2/3] Enhance MCP allowlist enforcement limitations details Updated the limitations section to include description and version matching for MCP allowlist enforcement. This is as per the current validation in the VS Code. --- content/copilot/reference/mcp-allowlist-enforcement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/reference/mcp-allowlist-enforcement.md b/content/copilot/reference/mcp-allowlist-enforcement.md index 2d69575f6164..7aa1a05cb4d9 100644 --- a/content/copilot/reference/mcp-allowlist-enforcement.md +++ b/content/copilot/reference/mcp-allowlist-enforcement.md @@ -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. From 4b1af4a8da64a25cb7abc2e5bc041a3e203696ae Mon Sep 17 00:00:00 2001 From: Manu PK Date: Sat, 10 Jan 2026 22:14:16 +0530 Subject: [PATCH 3/3] Changed to server name/ID to reflect better field. Changed to server name/ID to reflect better field. --- .../manage-mcp-usage/configure-mcp-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md b/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md index a10a91404000..7eae6ff02b6b 100644 --- a/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md +++ b/content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md @@ -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 name, description and version. 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)