Prerequisites
You may want to run a trial before enabling Copilot cloud agent for the enterprise. See Piloting GitHub Copilot cloud agent in your organization.
Enabling Copilot cloud agent
Copilot cloud agent and use of third-party MCP servers are disabled by default. You can enable these features for users who receive a Copilot license from your enterprise or organizations.
-
Navigate to your enterprise. For example, from the Enterprises page on GitHub.com.
-
At the top of the page, click AI controls.
-
In the left sidebar, click Agents.
-
Under "Available agents", click Copilot Cloud Agent.
-
Select a global policy for Copilot cloud agent, then communicate your decision with your organizations.
Tip
If you select Enabled for selected organizations, you can select individual organizations in the UI. To select organizations based on custom properties instead, use the REST API. See REST API endpoints for Copilot cloud agent management.
-
By default, the agent will be available in all repositories in selected organizations. If there are repositories where Copilot cloud agent should be blocked for all users, tell organization owners to configure this setting. See Adding GitHub Copilot cloud agent to your organization.
Enabling MCP servers
Copilot cloud agent automatically has access to a small number of default MCP servers. See Model Context Protocol (MCP) and GitHub Copilot cloud agent.
You can enable third-party MCP servers to allow developers to integrate Copilot cloud agent with other services in your DevOps toolchain, such as error-tracking platforms or logging systems.
- In the sidebar, click MCP.
- Set a policy for MCP servers in Copilot.
Note
The "MCP Registry URL" and "Restrict MCP access to registry servers" policies do not apply to Copilot cloud agent.