[WIP][MCP] Server Features in MCP configuration: API Tools, Dynamic Tool Mode, AL Query Tools (Preview)

[onbuyuka]

Summary

Adds a Server Features surface to the MCP configuration card so admins can opt configurations into the upcoming AL Query Tools (Preview) MCP runtime, alongside the existing Dynamic Tool Mode and API Tools controls. Each feature is a self-contained handler behind an interface, so the card is data-driven and extensible. The shape is intentional; storage and runtime hookups land once the platform-side pieces are in (see Pending platform dependencies below).

Feature handlers (interface-based)

• New interface "MCP Server Features" — SetActive / IsActive / HasSettings / OpenSettings / Description / LoadSystemTools. enum "MCP Server Feature" implements it, binding each value to a handler codeunit; resolving ServerFeature := Rec.Feature replaces the old per-feature case blocks.
• Both the MCP Server Feature List and MCP System Tool List pages are fully generic: each walks ServerFeature.Ordinals() + FromInteger(...) (the same pattern as MCP Config Warning Type) and dispatches every action — activation, settings, descriptions, and system-tool loading — through the handler. Adding a feature is a new enum value + handler codeunit — no page edits.
• Each feature owns its description, activation, settings, system tools, and rules; SetActive delegates to codeunit "MCP Config Implementation". Dynamic Tool Mode's handler is real (EnableDynamicToolMode / DiscoverReadOnlyObjects + the real system-tool catalog); API Tools and AL Query Tools are platform-pending stubs whose IsActive returns false until the config fields ship.

Card UX

• Server Features list-part with per-row Activate / Deactivate / Configure, mirroring page 7775 "Copilot AI Capabilities" → Copilot Capabilities GA. Configure appears only for features that have settings — gated on a per-row Configurable flag set from the handler's HasSettings().
  • API Tools — gates the Available APIs list-part (Visible = not IsDefault and APIToolsActive), where the admin curates which API pages / queries the client can reach. No settings.
  • Dynamic Tool Mode — its Configure dialog hosts Discover Additional Read-Only Objects; activation flows to EnableDynamicToolMode, deactivation cascade-clears DiscoverReadOnlyObjects. (A "requires API Tools enabled first" gate lives in impl.EnableDynamicToolMode as a commented PLATFORM-PENDING check — inactive until the API Tools field exists.)
  • AL Query Tools (Preview) — contributes the AL Query system tools when active. No settings (the earlier mock Max Rows / Query Timeout were dropped).
• The single settings StandardDialog (page 8369 "MCP Server Feature Settings") is used only by Dynamic Tool Mode; its handler runs it via OpenSettings, writing on OK.
• The System Tools list-part (right-rail FactBox, Server Feature column) is rebuilt by iterating the active features and calling each handler's LoadSystemTools. The curated-APIs list-part (page 8352) was renamed 'Available Tools' → 'API Tools' → 'Available APIs' to disambiguate it from the API Tools feature row.

Public API

• codeunit 8350 "MCP Config" exposes EnableAPITools and EnableALQueryTools — empty // MOCK: no-ops until the platform adds the corresponding MCP Configuration fields — alongside the existing EnableDynamicToolMode. Feature handlers persist activation through codeunit "MCP Config Implementation". (The earlier SetALQueryMaxRowsPerQuery / SetALQueryTimeoutSeconds procedures were removed with the mock sub-settings.)

New objects

• interface "MCP Server Features"
• enum 8351 "MCP Server Feature" (implements "MCP Server Features"; API Tools, Dynamic Tool Mode, AL Query Tools)
• table 8355 "MCP Server Feature" (temporary, in-app; carries a Configurable flag)
• page 8368 "MCP Server Feature List", page 8369 "MCP Server Feature Settings"
• handler codeunits 8369 "MCP API Tools Feature", 8368 "MCP AL Query Tools Feature", 8370 "MCP Dyn. Tool Mode Feature"

Pending platform dependencies

This PR is WIP pending platform-side work:

1. Activation boolean fields on MCP Configuration for API Tools and AL Query Tools — the handlers delegate to MCP Config Implementation (EnableAPITools / EnableALQueryTools), today empty no-ops, and IsActive returns false. The "API Tools required for Dynamic Tool Mode" gate in impl.EnableDynamicToolMode is commented out until the API Tools field lands.
2. MCP Utilities exposing the real AL Query system tool catalog (replacing the hardcoded compile_al_query / run_al_query inserts in the AL Query handler's LoadSystemTools).
3. The AL Query runtime itself (compile + execute of client-submitted code).

Once those land, each feature's wire-up is localized to its handler codeunit (and impl.Enable*) — grep -rn "MOCK:\|PLATFORM-PENDING:" src/System\ Application/App/MCP/ enumerates every site.

Test plan

• MCP Config Test (codeunit 130130): facade smoke tests for EnableAPITools and EnableALQueryTools (callable no-ops; // MOCK: placeholders to become real state assertions once the platform fields exist).
• Server Features TestPage tests on page 8351 "MCP Config Card": the list shows all three features in enum order, Configure is enabled only on Dynamic Tool Mode, activating Dynamic Tool Mode flips its row Status and sets EnableDynamicToolMode, and the part is hidden on the default configuration. (Also fixed TestDefaultConfigurationPage, which still referenced card fields D22 had moved into the Configure dialog.)
• Manual walkthrough of the Server Features list / Configure / Activate-Deactivate cycle against a local BC instance.

Fixes AB#631012

🤖 Generated with Claude Code

[github-actions]

AL Documentation Audit

Documentation gaps were detected in the following apps:

• MCP-Test: 0% documentation coverage
• MCP: 67% documentation coverage

To generate documentation, run /al-docs init or /al-docs update using GitHub Copilot CLI or Claude Code.
This review is for awareness to help keep documentation in sync with code changes. It is okay to dismiss this request.