MCP registry policies work for Copilot CLI (#60714)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: isaacmbrown

content/copilot/concepts/mcp-management.md

@@ -10,7 +10,7 @@ category:
   - Manage Copilot for a team
 ---
 
-You can manage Model Context Protocol (MCP) server usage in your organization or enterprise by configuring a series of MCP policies on {% data variables.product.prodname_dotcom_the_website %}. Through these policies, you can allow or block MCP server usage entirely, or restrict access to a list of servers that you define in an MCP registry.
+You can manage Model Context Protocol (MCP) server usage in your organization or enterprise by configuring a series of MCP policies on {% data variables.product.prodname_dotcom_the_website %}. Through these policies, you can allow or block MCP server usage entirely, or restrict access to a list of servers that you define in an MCP registry. These policies apply to supported IDEs and {% data variables.copilot.copilot_cli_short %}.
 
 ## MCP registries
 

content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md

@@ -41,16 +41,17 @@ For more details and example JSON responses to requests, see the [Official MCP R
 
 #### Support for the v0.1 specification
 
-While the MCP registry launched using the v0 specification, that version is now considered unstable and should not be implemented. Instead, create your registry according to the v0.1 specification, which is supported in the following IDEs:
+While the MCP registry launched using the v0 specification, that version is now considered unstable and should not be implemented. Instead, create your registry according to the v0.1 specification, which is supported in the following surfaces:
 
-| IDE           | v0.1 support |
+| Surface       | v0.1 support |
 | ---------------------- | ----------------- |
 | {% data variables.product.prodname_vscode_shortname %} Insiders | {% octicon "check" aria-label="Supported" %}  |
 | {% data variables.product.prodname_vscode_shortname %}   | {% octicon "check" aria-label="Supported" %} |
 | {% data variables.product.prodname_vs %}      | {% octicon "check" aria-label="Supported" %} |
 | Eclipse | {% octicon "check" aria-label="Supported" %} |
 | JetBrains IDEs     | {% octicon "check" aria-label="Supported" %} |
 | Xcode    | {% octicon "check" aria-label="Supported" %} |
+| {% data variables.copilot.copilot_cli_short %} | {% octicon "check" aria-label="Supported" %} |
 
 ### Cross-Origin Resource Sharing requirements
 

content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-server-access.md

@@ -1,6 +1,6 @@
 ---
 title: Configure MCP server access for your organization or enterprise
-intro: You can configure an MCP registry URL and access control policy to determine which MCP servers developers can discover and use in supported IDEs with {% data variables.product.prodname_copilot %}.
+intro: You can configure an MCP registry URL and access control policy to determine which MCP servers developers can discover and use in supported IDEs and {% data variables.copilot.copilot_cli_short %}.
 permissions: Enterprise owners and organization owners
 product: '{% data variables.copilot.copilot_enterprise_short %} or {% data variables.copilot.copilot_business_short %}'
 versions:

content/copilot/how-tos/copilot-cli/administer-copilot-cli-for-your-enterprise.md

@@ -38,6 +38,10 @@ Users can only access AI models that are enabled at the enterprise level. When y
 
 Enterprise-configured custom agents are available to use with {% data variables.copilot.copilot_cli_short %}.
 
+### MCP server policies
+
+Enterprise and organization MCP policies apply to {% data variables.copilot.copilot_cli_short %}. You can configure an MCP registry URL so developers can discover approved servers, and set an allowlist policy to restrict which MCP servers can run. For more information, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-server-access).
+
 ### {% data variables.copilot.copilot_cloud_agent %} enablement
 
 Both the {% data variables.copilot.copilot_cli_short %} policy and the {% data variables.copilot.copilot_cloud_agent %} policy must be enabled for users to be able to use the `/delegate` command in {% data variables.copilot.copilot_cli_short %}.
@@ -54,7 +58,6 @@ Users must have an assigned {% data variables.product.prodname_copilot %} seat t
 
 All other controls do **not** affect {% data variables.copilot.copilot_cli_short %}, notably:
 
-* **Model Context Protocol (MCP) server policies**: Enterprise policies that control whether MCP servers can be used, or which MCP registry servers are allowed
 * **IDE-specific policies**: Policies configured for specific IDEs or editor extensions
 * **Content exclusions**: File path-based content exclusions
 * **User-configured model providers (BYOK)**: Users can configure {% data variables.copilot.copilot_cli_short %} to use their own model providers via environment variables. This is configured at the _user level_ and cannot be controlled by enterprise policies.

content/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers.md

@@ -20,6 +20,8 @@ The Model Context Protocol (MCP) is an open standard that defines how applicatio
 > [!NOTE]
 > The {% data variables.product.github %} MCP server is built into {% data variables.copilot.copilot_cli_short %} and is already available without any additional configuration. The steps below are for adding other MCP servers.
 
+If your organization or enterprise has configured a registry URL and allowlist policy, those settings apply to {% data variables.copilot.copilot_cli_short %}. The configured registry URL will appear as a discovery source, and only servers permitted by the allowlist policy can run.
+
 You can add MCP servers using the interactive `/mcp add` command within the CLI, or by editing the configuration file directly.
 
 For installation instructions, available tools, and URLs for specific MCP servers, see the [{% data variables.product.github %} MCP Registry](https://github.com/mcp).