Improvement

April 16, 20261 Minute Read

Copilot CLI supports custom registry based MCP allowlists

Enterprise and organization administrators can now bring their own MCP registry and enforce allowlist policies in Copilot CLI. This feature is in public preview and brings MCP governance controls to developers working directly from the CLI.

What is bring your own registry?

Bring your own registry (BYOR) lets GitHub administrators use the URL of an internally managed MCP registry to their enterprise or organization’s Copilot policies page. Once configured, it prevents any usage of MCP servers (at runtime) that are not defined in your registry.

Getting started

This feature is available for Copilot Business and Copilot Enterprise customers. With bring your own registry support in Copilot CLI, you can now extend MCP governance controls to your terminal-based developer workflows.

For setup instructions and registry format specifications, see Configure an MCP registry for your organization or enterprise.

Subscribe to our developer newsletter

Discover tips, technical guides, and best practices in our biweekly newsletter just for devs.

By submitting, I agree to let GitHub and its affiliates use my information for personalized communications, targeted advertising, and campaign effectiveness. See the GitHub Privacy Statement for more details.

Copilot CLI supports custom registry based MCP allowlists - GitHub Changelog