|
| 1 | +--- |
| 2 | +title: MCP server usage in your company |
| 3 | +shortTitle: MCP management |
| 4 | +intro: 'You can manage MCP server usage to provide your developers with valuable tools while maintaining security and compliance.' |
| 5 | +versions: |
| 6 | + feature: copilot |
| 7 | +topics: |
| 8 | + - Copilot |
| 9 | +contentType: concepts |
| 10 | +--- |
| 11 | + |
| 12 | +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. |
| 13 | + |
| 14 | +## MCP registries |
| 15 | + |
| 16 | +An MCP registry is a directory of MCP servers that acts like a catalog for IDEs and {% data variables.product.prodname_copilot_short %}. Each registry entry points to a server's manifest, which describes the tools, resources, and prompts that server provides. |
| 17 | + |
| 18 | +After you create your MCP registry, you can make it available to your company, allowing you to: |
| 19 | +* Curate a catalog of MCP servers your developers can discover and use without context switching |
| 20 | +* Restrict access to unapproved servers for increased security and compliance |
| 21 | +* Provide clarity to developers when a server is blocked by policy |
| 22 | + |
| 23 | +## MCP policy settings |
| 24 | + |
| 25 | +The following settings let you control how MCP servers are discovered and accessed in your organization or enterprise: |
| 26 | + |
| 27 | +* **MCP servers in {% data variables.product.prodname_copilot_short %}**: Manage the use of MCP servers for all users with {% data variables.product.prodname_copilot_short %} seats in your organization or enterprise. |
| 28 | +* **MCP Registry URL**: Specify the URL of your MCP registry, allowing your developers to discover and use approved MCP servers in supported surfaces. |
| 29 | +* **Restrict MCP access to registry servers**: Choose whether to allow all MCP servers or restrict access to only those listed in your configured registry. |
| 30 | + |
| 31 | +## Supported surfaces |
| 32 | + |
| 33 | +MCP management features are supported as follows: |
| 34 | + |
| 35 | +| Surface | Registry display | Allowlist enforcement | |
| 36 | +|---|:---:|:---:| |
| 37 | +| {% data variables.copilot.copilot_cli_short %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} | |
| 38 | +| {% data variables.copilot.copilot_coding_agent %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} | |
| 39 | +| Eclipse | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | |
| 40 | +| JetBrains | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | |
| 41 | +| {% data variables.product.prodname_vs %} | {% octicon "x" aria-label="Not supported" %} | {% octicon "x" aria-label="Not supported" %} | |
| 42 | +| {% data variables.product.prodname_vscode_shortname %} | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | |
| 43 | +| {% data variables.product.prodname_vscode_shortname %} Insiders | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | |
| 44 | +| Xcode | {% octicon "check" aria-label="Supported" %} | {% octicon "check" aria-label="Supported" %} | |
| 45 | + |
| 46 | +> [!NOTE] |
| 47 | +> For Eclipse, JetBrains, and Xcode, MCP management features are supported in the pre-release versions of {% data variables.product.prodname_copilot_short %}. |
| 48 | +
|
| 49 | +## Next steps |
| 50 | + |
| 51 | +To create your own MCP registry, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry). |
0 commit comments