Expose user-managed MCP tools without manual starter-profile edits #311
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/native-mcp-managed-tool-exposure"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #310 found during actual-use verification: the starter Core tool selection allowed connecting/authenticating a server but did not declare direct MCP tools to the model. The native user-management integration now reserves MCP/codemode/tool-search entrypoints when building the SDK tool selection; no server starts until explicitly enabled and configured. Existing mcp__ tool/namespace restrictions still filter servers, tools: [] still exposes nothing, unrelated non-MCP tools are not added, ephemeral assessment sessions remain tool-free, and bare SDK embedders preserve their existing explicit selection. Real stdio regression enables MCP on an already-open read-only-base session, proves its configured direct tool becomes ACTIVE, and proves bash remains unavailable. Explicit MCP namespace-filter regression also passes. Typecheck and full suite: 1660 passed, one optional skip, zero failed.