Interface "MCP Server Features"
System Application · System.MCP
Across versions
- BC23-28not present
- BC29-30present
System Application · System.MCP · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
SetActive(ConfigId: Guid; Active: Boolean): Activates or deactivates the feature for the specified MCP configuration.IsActive(ConfigId: Guid): Boolean: Returns whether the feature is currently active for the specified MCP configuration.HasSettings(): Boolean: Returns whether the feature exposes additional settings (drives the Configure action).OpenSettings(ConfigId: Guid): Opens the feature’s settings dialog. No-op when HasSettings() returns false.Description(): Text[500]: Returns the description shown for the feature in the Server Features list.LoadSystemTools(var MCPSystemTool: Record "MCP System Tool"): Appends the feature’s system tools to the buffer. Called only when the feature is active.TryGetParentFeature(var ParentFeature: Enum "MCP Server Feature"): Boolean: Returns true and the parent feature when this is a sub-feature. The Server Features list shows a sub-feature indented beneath its parent.
Implemented by
- Codeunit 8368 “MCP Data Query Tools Feature”
- Codeunit 8369 “MCP API Tools Feature”
- Codeunit 8370 “MCP Dyn. Tool Mode Feature”
- Enum 8351 “MCP Server Feature”
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: "interface", object_name: "MCP Server Features"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.