{"version":"2.1.283","anchor":"cloud-mcp-passthrough-now-offers-no-servers-when-its-approva","canonical_anchor":"cloud-mcp-passthrough-now-offers-no-servers-when-its-approva","heading":"Cloud sessions get no MCP servers from this machine when its approval state is unreadable","tier":"notice","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/cloud-mcp-passthrough-now-offers-no-servers-when-its-approva","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sessions get no MCP servers from this machine when its approval state is unreadable\n\nIf this machine's MCP passthrough approval state cannot be read, no MCP servers are offered to cloud sessions and a one-time notice says so\n\n**Unclear.** It is unclear whether only the notice is new or the handling of an unreadable record too, and what switches passthrough on.\n\n**What**\n\nMCP servers are outside tools connected to Claude Code through the Model Context Protocol. MCP passthrough offers the MCP servers you approved on this machine to cloud sessions (sessions running on remote machines). Claude Code keeps a saved record of which servers are approved.\n\nWhen that record cannot be read, Claude Code now offers no MCP servers to cloud sessions and shows a one-time notice saying so. Before, it fell back to the previous state.\n\n**Why**\n\nWhen it is unknown which servers were approved, none are exposed to cloud sessions rather than possibly the wrong ones. If your cloud session is missing tools, this notice explains why.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}