Codeunit 8369 "MCP API Tools Feature"

System Application · System.MCP · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• SetActive(ConfigId: Guid; Active: Boolean)
• IsActive(ConfigId: Guid): Boolean
• HasSettings(): Boolean
• OpenSettings(ConfigId: Guid)
• Description(): Text[500]
• LoadSystemTools(var MCPSystemTool: Record "MCP System Tool")
• TryGetParentFeature(var ParentFeature: Enum "MCP Server Feature"): Boolean

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 8351 “MCP Config Implementation” (2 calls: IsActive → IsAPIToolsEnabled, SetActive → EnableAPITools)

Implements

• Interface “MCP Server Features”

Recent changes

• 2026-07-27 #8085 [MCP] Server Features in MCP configuration: API Tools, Dynamic Tool Mode, Data Query Tools (Preview) (main, BC30, feature, added)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "MCP API Tools Feature"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.