{"version":"2.1.323","anchor":"device-mcp-bridge-now-serves-mcp-task-requests-mcp-task-wi","canonical_anchor":"device-mcp-bridge-now-serves-mcp-task-requests-mcp-task-wi","heading":"Cloud sessions can run MCP tasks through your computer's shared servers","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/device-mcp-bridge-now-serves-mcp-task-requests-mcp-task-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Cloud sessions can run MCP tasks through your computer's shared servers\n\nThe bridge sharing your computer's MCP servers with a cloud session now handles task requests, rechecking several conditions before each one\n\n**What**\n\nClaude Code can share the MCP servers on your computer (MCP is the protocol for connecting external tools) with a cloud session. That bridge can now also handle MCP task requests, which are for longer-running tool jobs. It refuses a request, each with its own error, when:\n\n- The connections are being rebuilt.\n\n- Your computer's offered tools changed while the request was being checked.\n\n- The server was not offered to the cloud session.\n\n- The server has not connected yet.\n\nA request to cancel a task is still passed on for a blocked tool before the request is refused.\n\n**Why**\n\nCloud sessions can drive long-running MCP tool jobs on your machine, while consent and policy are checked again on every request.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}