跳到正文
FunCoding

搜索

搜索文档、文章、Skill 和 MCP

Restrict MCP server access to a custom registry

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.

This feature is in public preview and is not the recommended method for restricting access to MCP servers. The more secure, generally available method is to define settings in your enterprise's managed-settings.json file. See AUTOTITLE.

Prerequisites

Before you can fully configure MCP server access for your company, you need to create an MCP registry. See AUTOTITLE.

Configuring the MCP allowlist policy for an enterprise

To ensure uniform access, you can set and maintain your MCP registry URL and allowlist policy at the enterprise level. Otherwise, if your teams have different needs, you should configure separate policies for each organization.

  1. Navigate to your enterprise. For example, from the Enterprises page on GitHub.com.

  2. At the top of the page, click copilot AI controls.

  3. In the sidebar, click mcp MCP.

  4. Ensure MCP servers in Copilot is set to Enabled everywhere.

  5. In the MCP Registry URL section, enter the URL of your registry, then click Save.

If you set up your MCP registry using Azure API Center, enter the base URL for your API Center, including the workspace path, in the format:

https://SERVICE-NAME.data.REGION.azure-apicenter.ms/workspaces/WORKSPACE-NAME

For example:

https://contoso-apic.data.eastus.azure-apicenter.ms/workspaces/default

Including additional route suffixes like /v0.1/servers will cause the registry to error out, because GitHub Copilot appends the MCP v0.1 path automatically.

  1. In the Restrict MCP access to registry servers section, select the dropdown menu, then click one of the following options:

    • Allow all: No restrictions. All MCP servers can be used.
    • Registry only: Only servers from the registry may run.

    Your chosen policy will immediately apply to developers in your enterprise.

Configuring the MCP allowlist policy for an organization

  1. In the upper-right corner of GitHub, click your profile picture, then click organization Organizations.

  2. Select an organization by clicking on it.

  3. Under your organization name, click gear Settings. If you cannot see the "Settings" tab, select the More dropdown menu, then click Settings.

    Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.

  4. In the sidebar, under "Code, planning, and automation", click copilot Copilot, then click Policies.

  5. In the "Features" section, ensure MCP servers in Copilot is set to Enabled.

  6. In the MCP Registry URL (optional) field, enter the URL of your registry, then click Save.

If you set up your MCP registry using Azure API Center, enter the base URL for your API Center, including the workspace path, in the format:

https://SERVICE-NAME.data.REGION.azure-apicenter.ms/workspaces/WORKSPACE-NAME

For example:

https://contoso-apic.data.eastus.azure-apicenter.ms/workspaces/default

Including additional route suffixes like /v0.1/servers will cause the registry to error out, because GitHub Copilot appends the MCP v0.1 path automatically.

  1. In the Restrict MCP access to registry servers section, select the dropdown menu, then click one of the following options:

    • Allow all: No restrictions. All MCP servers can be used.
    • Registry only: Only servers from the registry may run.

    Your chosen policy will immediately apply to developers in your organization.

Next steps

For detailed information on MCP allowlist enforcement and limitations, see AUTOTITLE.

Further reading