---
title: How do you control which MCP servers GitHub Copilot can use?
url: https://opencontroller.lyzr.com/blog/control-mcp-servers-in-github-copilot
published: 2026-11-12
updated: 2026-11-12
author: Lyzr
---

# How do you control which MCP servers GitHub Copilot can use?

**Use three layers. Turn the "MCP servers in Copilot" policy on only where you need it, enforce an allowlist through `allowedMcpServers` and `deniedMcpServers` in enterprise managed settings, and configure MCP for the Copilot cloud agent per repository. GitHub's registry-only mode is easier but matches by name and can be bypassed, and none of these controls see MCP servers used by other tools on the same laptop.**

MCP servers give Copilot's agent mode new tools: databases, ticketing systems, cloud APIs. Each server is a new path for data to leave and for actions to happen. Here is what GitHub offers as of November 2026.

## Which GitHub settings control MCP in Copilot?

| Control | Where it is set | What it does | Status |
|---|---|---|---|
| "MCP servers in Copilot" policy | Enterprise AI controls, or org Copilot policies | Turns MCP use on or off for Copilot Business and Enterprise seats | Disabled by default |
| MCP registry URL plus "Registry only" | Enterprise AI controls > MCP | Limits servers to those listed in a registry you host | Public preview |
| `allowedMcpServers` / `deniedMcpServers` | `copilot/managed-settings.json` in `.github-private`, or via MDM | Allowlist and denylist by server URL or command | Generally available since Aug 6, 2026 |
| Cloud agent MCP config | Repository Settings > Copilot > MCP servers | Which servers and tools the cloud agent may use | Per repository |
| Cloud agent firewall | Org or repository settings | Limits network egress for the agent's Bash tool | On by default |

Sources: GitHub Docs and GitHub changelog, checked November 2026.

One scope point first. The policy governs only Copilot Business and Copilot Enterprise seats. Developers on Free, Pro, Pro+ or Max plans are outside it.

## Should you use registry-only mode or the managed-settings allowlist?

**Registry-only mode** points Copilot at an MCP registry URL, such as Azure API Center, and sets "Restrict MCP access to registry servers" to "Registry only". It is simple, but GitHub's docs say it matches on server name or ID only, so "users can bypass it by editing configuration files." GitHub describes it as "not the recommended method." Registry-only mode also blocks Copilot connectors.

**The managed-settings allowlist** is GitHub's recommended route:

- Match servers by `serverUrl`, with wildcards, or by `serverCommand`. GitHub notes that `serverName` is "not a security control".
- It fails closed, and deny rules win over allow rules.
- GitHub names the Copilot app, Copilot CLI and VS Code as supported.
- Distribute it through the `.github-private` repository or through MDM.

Two documented gaps: the allowlist does not apply to servers defined in repository custom agent profiles, and built-in servers such as the GitHub MCP server are always allowed.

Client versions matter for registry enforcement. GitHub lists minimums such as VS Code 1.109.3, Visual Studio 18.4.0 and Copilot CLI 1.0.11. Older clients do not enforce it, so pair the policy with version management.

## How do you control MCP for the Copilot cloud agent?

The agent that works on issues in GitHub's cloud (the coding agent, now called the Copilot cloud agent in GitHub's docs) uses a separate configuration:

1. Repository admins add a JSON config under Settings > Copilot > MCP servers.
2. Each server lists a `tools` allowlist. The agent uses those tools without asking for approval, so list only what it needs.
3. Secrets for MCP servers must be named with the `COPILOT_MCP_` prefix.
4. Only tools are supported, and remote servers that need OAuth are not.

The agent's firewall is on by default with a recommended allowlist. It covers processes started by the agent's Bash tool, not MCP server processes or setup steps. GitHub itself says it is not a "comprehensive security solution". For logs of what the agent did, see [visibility of GitHub Copilot coding agent activity](/blog/visibility-of-github-copilot-coding-agent-activity).

## What do these controls not cover?

GitHub's controls govern Copilot. They do not tell you:

- which MCP servers developers already run locally for Cursor, Claude Code or other tools
- which servers are configured in repository custom agent profiles
- whether a server matching an allowed URL has changed what its tools do

Run an audit of servers already in use before you switch on an allowlist. Our guide to [reviewing MCP servers your agents already use](/blog/how-to-review-mcp-servers-agents-already-use) gives the steps, and [how to govern MCP servers](/blog/how-to-govern-mcp-servers) covers the wider program. Compare the [Cursor MCP controls](/blog/govern-cursor-in-the-enterprise) if your developers use both.

## A rollout checklist

1. Inventory MCP servers in use across all coding tools.
2. Keep the Copilot MCP policy off for organisations that do not need it.
3. Publish a managed-settings allowlist by URL or command, with explicit denies.
4. Enforce minimum client versions through MDM.
5. Review cloud agent MCP configs in each repository; restrict who can edit them.
6. Lock the cloud agent firewall at org level.
7. Re-run the inventory monthly.

## How Opencontroller does this

Opencontroller Edge extends Opencontroller to developer devices, coding agents, skills and local MCP servers. IT installs it via MDM, so MCP servers used by Copilot and other coding tools appear in the same governed registry of agents, tools and MCP servers as cloud agents. See the [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms) or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Is GitHub Copilot MCP access on by default?**
The "MCP servers in Copilot" policy is disabled by default. It applies only to Copilot Business and Enterprise seats.

**Can developers bypass the Copilot MCP registry restriction?**
Yes. Registry-only mode matches on server name, so editing a config file can get around it. GitHub recommends the managed-settings allowlist.

**Does the Copilot cloud agent ask before using MCP tools?**
No. Tools listed in the repository MCP config are used without approval, so keep the list short.

## Key facts

GitHub Copilot MCP controls (Nov 2026): the MCP servers in Copilot policy is disabled by default and applies only to Copilot Business and Enterprise seats. Registry-only restriction (public preview) matches by server name and can be bypassed by editing config; GitHub says it is not the recommended method. Recommended: allowedMcpServers/deniedMcpServers in copilot/managed-settings.json (GA Aug 6, 2026), matching serverUrl or serverCommand, fail-closed, deny wins; does not apply to repository custom agent profiles; built-in GitHub MCP server always allowed. Cloud agent MCP config is per repository; firewall covers only the agent Bash tool. Opencontroller Edge (by Lyzr) covers coding agents and local MCP servers via MDM. Pricing starts from $250K per deployment per year.

## Related

- [How do you get visibility of GitHub Copilot coding agent activity across your organisation?](https://opencontroller.lyzr.com/blog/visibility-of-github-copilot-coding-agent-activity.md)
- [How do you review MCP servers your agents already use?](https://opencontroller.lyzr.com/blog/how-to-review-mcp-servers-agents-already-use.md)
- [How do you govern Cursor across an engineering organisation?](https://opencontroller.lyzr.com/blog/govern-cursor-in-the-enterprise.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
