#10008 [MCP] Add codeunit APIs as MCP tools in MCP configuration

Pull request · merged into main (BC30) on 2026-08-20 by onbuyuka · 13 files (+615 -269), 10 AL · feature · tier official · reviewed (checked by Opus)

What changed

• Codeunits are added as an MCP tool object type, at parity with API pages and queries, with a new CreateCodeunitAPITool facade
• API metadata for pages, queries and codeunits now comes from the Api Web Service table, and only published APIs are listed
• The API Overview page lists pages, queries and codeunits, and its Entity column shows the entity set name
• Allow Bound Actions is renamed to Allow Actions; AllowBoundActions is deprecated, and for codeunit tools Allow Actions is the invoke toggle
• Microsoft and standard beta pages are excluded from selection, while third-party beta pages stay available
• Behaviour changes for users or extensions.

AL objects touched

• Page 812 “API Overview”, Base Application: modified
• Table 812 “API Overview Buffer”, Base Application: modified
• Codeunit 8350 “MCP Config”, System Application: modified
• Codeunit 8351 “MCP Config Implementation”, System Application: modified
• Codeunit 8353 “MCP Config Missing Object”, System Application: modified
• Codeunit 8354 “MCP Config Missing Parent”, System Application: modified
• Codeunit 8356 “MCP Upgrade”, System Application: modified
• Page 8376 “MCP API Object Lookup”, System Application: modified
• Page 8352 “MCP Config Tool List”, System Application: modified
• Table 8357 “MCP API Object Buffer”, System Application: modified

Context

• Work items: AB#643238
• Labels: AL: System Application, Team: Integrations
• Systems: development, integration
• From the description: “Adds Codeunit as a new object type in the MCP configuration UI, at parity with API pages and queries”

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).