You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 39e4601
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-mcp-registry.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ At its core, an MCP registry is a set of HTTPS endpoints that serve details abou
24
24
* Publish your own custom implementation.
25
25
26
26
> [!NOTE]
27
-
> 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).
27
+
> If you want your developers to have access to local MCP servers, include those servers in your registry with the correct server name, description and version. For more information, see [AUTOTITLE](/copilot/reference/mcp-allowlist-enforcement).
28
28
29
29
To create a valid MCP registry that is reachable by {% data variables.product.prodname_copilot %}, the registry must meet the following requirements:
30
30
*[Endpoint and specification requirements](#endpoint-and-specification-requirements)
0 commit comments