Answer: GitHub Copilot controls which MCP servers are used in your company by configuring MCP policies on GitHub, including the "MCP servers in Copilot" policy that defines whether MCP servers can run at all, and by restricting servers to an approved list via an allowlist. The recommended allowlist method is the enterprise's managed-settings.json file, which applies settings across clients that users cannot override. Status: Confirmed Entry: tool/github-copilot/admin-and-enterprise/mcp-server-usage-company Revision: 3 Digest: sha256:c1b0896446bb4d84 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:20:53Z Last changed: 2026-11-19T12:51:01Z (server matching method: — → Secure matching based on name, URL, or stdio commands) Last verified: 2026-11-20T12:57:04Z Next check: 2026-11-21T12:57:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of policy | MCP servers in Copilot | [1] | 2026-11-20 recommended allowlist method | managed-settings.json | [1] | 2026-11-20 alternative method | host your own MCP registry | [1] | 2026-11-20 enforcement level | Enterprise-wide settings, overridable for enterprise teams | [1] | 2026-11-20 server matching method | Secure matching based on name, URL, or stdio commands | [1] | 2026-11-20 Sources: [1] GitHub. "MCP server usage in your company - GitHub Docs". https://docs.github.com/en/copilot/concepts/enterprise/mcp-management Role: primary. Accessed: 2026-11-20T12:57:04Z Quote: "The MCP servers in Copilot policy defines whether MCP servers can run at all across Copilot clients." (Supports: policy) Quote: "The recommended method for creating an allowlist is to use your enterprise's managed-settings.json file." (Supports: recommended allowlist method) Quote: "Alternatively, you can host your own MCP registry and restrict access to servers in the registry." (Supports: alternative method) Quote: "Enterprise-wide settings, overridable for enterprise teams" (Supports: enforcement level) Quote: "Secure matching based on name, URL, or stdio commands" (Supports: server matching method) Snapshot SHA-256: 672e15a7441d026671b154e37fd9f98598843892ed4a7c4d9b789a494b7d4784 (captured 2026-11-18T12:50:41Z) 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:50:41Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:57:04Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:57:04Z Last attempt: 2026-11-20T12:57:04Z Notes and limitations: Extracted automatically from a single official source (section "MCP server usage in your company"). Related: https://latestn.com/tool/github-copilot/admin-and-enterprise/mdm-file-based-settings-without-orgs How do I use MDM-managed or file-based settings for GitHub Copilot Business without organizations? https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-adoption-outcomes How do I measure sustained usage and team outcomes after a GitHub Copilot adoption sprint? https://latestn.com/tool/github-copilot/admin-and-enterprise/measure-copilot-impact How do I measure and demonstrate the impact of GitHub Copilot adoption? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-allowlist How do I allow or deny MCP servers in GitHub Copilot enterprise settings? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-enterprise-config How do I configure the GitHub MCP server for an enterprise with GitHub Copilot? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-enterprise-prerequisites What are the prerequisites for configuring the GitHub MCP Server for GitHub Enterprise? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:51:01Z | changed | server matching method: — → Secure matching based on name, URL, or stdio commands | [1] 2026-11-19T12:51:01Z | changed | enforcement level: — → Enterprise-wide settings, overridable for enterprise teams | [1] 2026-11-19T12:51:01Z | changed | alternative method: — → host your own MCP registry | [1] 2026-11-19T12:51:01Z | changed | recommended allowlist method: — → managed-settings.json | [1] 2026-11-19T12:51:01Z | changed | policy: — → MCP servers in Copilot | [1] 2026-11-19T12:51:01Z | changed | Custom registry server matching: Less secure matching, based on name or ID only → — | [1] 2026-11-19T12:51:01Z | changed | Managed settings server matching: Secure matching based on name, URL, or stdio commands → — | [1] 2026-11-19T12:51:01Z | changed | Custom registry release phase: Public preview, not prioritized for development → — | [1] 2026-11-19T12:51:01Z | changed | Managed settings release phase: Generally available → — | [1] 2026-11-19T12:51:01Z | changed | Alternative method: host your own MCP registry → — | [1] 2026-11-19T12:51:01Z | changed | Recommended allowlist method: managed-settings.json → — | [1] 2026-11-19T12:51:01Z | changed | Policy name: MCP servers in Copilot → — | [1] 2026-11-17T13:11:43Z | changed | Custom registry server matching: — → Less secure matching, based on name or ID only | [1] 2026-11-17T13:11:43Z | changed | Managed settings server matching: — → Secure matching based on name, URL, or stdio commands | [1] 2026-11-17T13:11:43Z | changed | Custom registry release phase: — → Public preview, not prioritized for development | [1] 2026-11-17T13:11:43Z | changed | Managed settings release phase: — → Generally available | [1] 2026-11-17T13:11:43Z | changed | Alternative method release phase: Public preview, not prioritized for development → — | [1] 2026-11-17T13:11:43Z | changed | Alternative method: Custom registry → host your own MCP registry | [1] 2026-11-17T13:11:43Z | changed | Server matching method (managed settings): Secure matching based on name, URL, or stdio commands → — | [1] 2026-11-17T13:11:43Z | changed | Enforcement level (managed settings): Enterprise-wide settings, overridable for enterprise teams → — | [1] 2026-11-13T03:20:53Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company/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/admin-and-enterprise/mcp-server-usage-company POST: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How does GitHub Copilot control which MCP servers are used in my company? Revision 3, last verified 2026-11-20T12:57:04Z. https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company (accessed 2026-11-21T09:57:19Z). @misc{LatestN_tool_github_copilot_admin_and_enterprise_mcp_server_usage_company_r3, title = {How does GitHub Copilot control which MCP servers are used in my company?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-server-usage-company}}, note = {Revision 3; digest sha256:c1b0896446bb4d84; last verified 2026-11-20T12:57:04Z; accessed 2026-11-21T09:57:19Z} } 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/admin-and-enterprise/mcp-server-usage-company