Протокол контекста модели (MCP) — это открытый стандарт, определяющий, как приложения используют контекст с большими языковыми моделями (LLM). MCP предоставляет стандартный способ подключения моделей ИИ к различным источникам данных и средствам, что позволяет им эффективнее работать вместе.
You can manage MCP server usage in your organization or enterprise by configuring MCP policies on GitHub.
The MCP servers in Copilot policy defines whether MCP servers can run at all across Copilot clients. We recommend keeping this policy enabled and, if necessary, restricting the MCP servers that users can run to an approved list.
MCP allowlists
The recommended method for creating an allowlist is to use your enterprise's managed-settings.json file. This allows you to apply settings across clients that users cannot override.
Alternatively, you can host your own MCP registry and restrict access to servers in the registry. However, this method has weaker enforcement than managed-settings.json.
| Method | Managed settings file | Custom registry |
|---|---|---|
| Release phase | Generally available | Общедоступная предварительная версия, not prioritized for development |
| Ease of setup | You can host a configuration file on GitHub that applies automatically to clients. | You must host your own registry that matches the MCP specification and serves HTTPS requests. |
| Enforcement level | Enterprise-wide settings, overridable for enterprise teams | Enterprise-wide or for individual organizations |
| Supported clients | Clients supported by the managed-settings.json file, see Getting started with enterprise-managed settings. Planned to expand in the near future. | See Принудительное применение частного реестра MCP. |
| Server matching method | Secure matching based on name, URL, or stdio commands | Less secure matching, based on name or ID only. Users can bypass the restriction by editing configuration files. |
Next steps
To configure an allowlist on GitHub, see Настройка списка разрешений сервера MCP для предприятия.