Answer: You can restrict MCP server access to a custom registry by configuring an MCP registry URL and access control policy, which determines which MCP servers developers can discover and use in supported IDEs and Copilot CLI. Status: Confirmed Entry: tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry Revision: 3 Digest: sha256:b488538ed869ad4f (changes whenever the content changes) Timeline: Created: 2026-11-15T13:06:12Z Last changed: 2026-11-18T12:55:05Z (method: — → configure an MCP registry URL and access control policy) Last verified: 2026-11-20T13:01:02Z Next check: 2026-11-21T13:01:02Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of method | configure an MCP registry URL and access control policy | [1] | 2026-11-20 Sources: [1] GitHub. "Managing MCP usage in your company - GitHub Docs". https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-mcp-usage Role: primary. Accessed: 2026-11-20T13:01:02Z Quote: "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 Copilot CLI." (Supports: method) Snapshot SHA-256: 095714129f48d90d8ae598eb7b12290de4fd7c0a1934f1e1399a2430185249d7 (captured 2026-11-18T12:55:05Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T12:55:05Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:01:02Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:01:02Z Last attempt: 2026-11-20T13:01:02Z Notes and limitations: Extracted automatically from a single official source (section "Restrict MCP server access to a custom registry"). Related: https://latestn.com/tool/github-copilot/permissions-and-security/review-always-allowed-apps How do I review or manage always allowed applications for GitHub Copilot computer use? https://latestn.com/tool/github-copilot/permissions-and-security/review-app-before-approving How do I review a GitHub App before approving its access to my organization's Copilot? https://latestn.com/tool/github-copilot/permissions-and-security/review-content-exclusion-changes-repository How do I review changes to content exclusions for GitHub Copilot in my repository? https://latestn.com/tool/github-copilot/permissions-and-security/repository-insights-access Who can view GitHub Copilot Repository insights for a repository? https://latestn.com/tool/github-copilot/permissions-and-security/reset-tool-permissions How do I reset persisted tool permissions in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/permissions-and-security/restrict-available-tools How do I restrict which tools are available to the AI model in GitHub Copilot CLI? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T12:55:05Z | changed | method: — → configure an MCP registry URL and access control policy | [1] 2026-11-18T12:55:05Z | changed | configuration method: configure an MCP registry URL and access control policy → — | [1] 2026-11-16T12:44:26Z | changed | configuration method: — → configure an MCP registry URL and access control policy | [1] 2026-11-16T12:44:26Z | changed | Configuration method: configure an MCP registry URL and access control policy → — | [1] 2026-11-15T13:06:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry POST: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I restrict GitHub Copilot MCP server access to a custom registry? Revision 3, last verified 2026-11-20T13:01:02Z. https://latestn.com/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry (accessed 2026-11-21T10:06:18Z). @misc{LatestN_tool_github_copilot_permissions_and_security_restrict_mcp_to_custom_registry_r3, title = {How do I restrict GitHub Copilot MCP server access to a custom registry?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry}}, note = {Revision 3; digest sha256:b488538ed869ad4f; last verified 2026-11-20T13:01:02Z; accessed 2026-11-21T10:06:18Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/permissions-and-security/restrict-mcp-to-custom-registry