{"version":"2.1.267","anchor":"session-served-bridge-mcp-tool-routing-gains-a-not-yet","canonical_anchor":"session-served-bridge-mcp-tool-routing-gains-a-not-yet","heading":"Session-served ('bridge') MCP tool routing gains a 'not yet presentable' refusal path","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/session-served-bridge-mcp-tool-routing-gains-a-not-yet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Session-served ('bridge') MCP tool routing gains a 'not yet presentable' refusal path\n\nMCP tools served through a session bridge can now be refused as 'not yet presentable' instead of silently falling through\n\n**What**\n\nWhen Claude Code routes a call to an MCP tool (a tool provided by an external MCP server) served through a session bridge, it now checks a per-session record of that tool's state. If the tool is registered but its provider reports it isn't ready to be shown yet, the call now returns a `not_served` error directly, rather than falling through to try local or remote dispatch as it did before.\n\n**Why**\n\nThis should prevent Claude Code from attempting to use a bridge-served tool before it's actually ready, giving a clearer error instead of an unpredictable fallback attempt.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.267; this account: off, anonymous baseline: off, compiled default: off)\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}