#8634 [MCP] Register MCP server as a Copilot capability
The MCP server is now registered as a Copilot capability on the Copilot & agent capabilities page, allowing administrators to activate or deactivate it. Deactivating the capability updates the Copilot Settings status, which the platform reads to control MCP availability.
- 9files
- 6AL files
- 6objects
Pull request · merged into main (BC30) on 2026-07-21 by onbuyuka · 9 files (+187 -0), 6 AL · feature · tier official · reviewed (checked by Opus)
What changed
- MCP server registered as a Generally Available, not billed Copilot capability with the standard Activate/Deactivate flow
- Capability registered on install, on upgrade (tagged), and through the Copilot capabilities page subscriber
- MCP Config List and Card pages show a notification when the capability is deactivated, with an action to open the capabilities page
- Deactivating leaves existing MCP configurations untouched, so re-activating restores the feature immediately
- Platform-side rejection of MCP requests when the capability is inactive is a separate follow-up change
- Behaviour changes for users or extensions.
AL objects touched
- Codeunit 8358 “MCP Copilot Cap. Reg.”, System Application: added
- Codeunit 8359 “MCP Notifications”, System Application: added
- Codeunit 8352 “MCP Install”, System Application: modified
- Codeunit 8356 “MCP Upgrade”, System Application: modified
- Page 8351 “MCP Config Card”, System Application: modified
- Page 8350 “MCP Config List”, System Application: modified
Context
- Work items: AB#641612
- Labels: AL: System Application, Team: Integrations
- Systems: development
Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).