Copilot CLI Now Supports Custom MCP Registry Allowlists
Copilot CLI now lets enterprise admins enforce custom MCP registry allowlists, blocking unapproved servers at runtime. Available in public preview for Business and Enterprise plans.
TL;DR
- Copilot CLI now supports bring-your-own MCP registry (BYOR) for enterprise governance
- Admins can enforce allowlists that block unapproved MCP servers at runtime
- Available now in public preview for Copilot Business and Enterprise customers
New
- Bring Your Own Registry (BYOR) — Admins can point Copilot CLI to an internally managed MCP registry URL, blocking any MCP servers not explicitly defined in that registry at runtime
- MCP Governance in the Terminal — Extends existing MCP allowlist controls from the IDE to CLI-based developer workflows
Who Gets This
- Copilot Business and Copilot Enterprise customers only
- Configure via your organization or enterprise Copilot policies page
For setup details and registry format specs, see the GitHub docs on MCP registry configuration. This feature is in public preview.
Source: GitHub Changelog
