refactor(devframe): move cli.mcp to createCac options - #337
Conversation
Whether to expose an MCP route is a hosting decision made at the CLI assembly stage, not a capability of the tool. Add `mcp` to CreateCacOptions and read it as the flag default; deprecate the definition's `cli.mcp` (still honored as a fallback for now).
◈ PR Lens
Architecture 2 components touched across 2 lanes. Data flow
Drill down
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Whether to expose an MCP route is a hosting decision made at the CLI assembly stage, not a capability of the tool itself. This moves the MCP toggle to where hosting decisions belong.
What changed
mcp?: boolean | McpRouteOptionstoCreateCacOptions;createCacreads it as the default for the--mcpflag, with precedence--mcp/--no-mcp>createCac({ mcp })> deprecateddef.cli?.mcp.DevframeCliOptions.mcpon the definition. It is still honored as a fallback for now and will be removed in a future release.createCac({ mcp })pattern.mcp: truefrom its definition to itscreateCaccall so the reference example models the current pattern.The programmatic-host fallbacks (
initDevframe/initHub/createDevServerreadingdef.cli?.mcp) and the hub's DF8005 warning stay in place for the deprecation window and will be dropped once the field is removed.This PR was created with the help of an agent.