MCP servers, registries, and allow lists
GH-600 · Lesson 5 of 16 · 39:17
YouTube loads only after you press play. This chapter opens at its timestamp in the full course. Watch on YouTube ↗
In this lesson
Prepare for the GH-600 exam (GitHub Certified: Agentic AI Developer). In this lesson: adding local and remote MCP servers to the cloud agent (JSON in the repository settings, type and tools, keys in COPILOT_MCP_ secrets) and to custom agents, the remote GitHub MCP server in IDEs and in the cloud agent (read-only by default, toolsets, a fine-grained token or a GitHub App for wider access), MCP registries (the v0.1 specification, self-hosting, Azure API Center, public preview), and MCP allow lists with the enterprise's managed-settings.json, where a deny entry always wins. Includes three original practice questions.
Preview the topics
- Contoso’s cloud agent must read issues and pull requests in two other repositories of the organization, through the GitHub MCP server. What should the team configure?
- Contoso’s developers cannot find the approved MCP servers among hundreds of public ones in their IDE. What should the organization set up?
- Contoso’s enterprise must ensure that only approved MCP servers run, matched by URL or exact command, in a way that users cannot bypass by editing their configuration. What should the enterprise owners use?