{"version":"2.1.285","anchor":"mcp-connect-capability-and-worker-wake-outcome-callback","canonical_anchor":"mcp-connect-capability-and-worker-wake-outcome-callback","heading":"MCP tool calls made from task code can now connect to a server","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/mcp-connect-capability-and-worker-wake-outcome-callback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### MCP tool calls made from task code can now connect to a server\n\nThe link that lets task code call MCP tools can now also connect to a named MCP server, and one callback's errors are logged and ignored\n\n**Unclear.** How this new connect ability is exposed to users is not clear.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Claude Code has a link that lets code run by a task call tools on these servers. That link used to offer only a way to call a tool. It now also offers a way to connect to a named server.\n\nSeparately, when a task's background worker wakes up, Claude Code can report the outcome to a piece of code. If that code fails, the error is now logged and ignored rather than passed on.\n\n**Why**\n\nTask code can now ask Claude Code to connect to an MCP server instead of only calling tools on one that is already connected. A failure while reporting a worker's wake-up no longer interrupts the task.\n\n- Flag `tengu_mcp_legacy_sse_fallback`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}