{"version":"2.1.283","anchor":"new-consent-prompt-lets-claude-cloud-sessions-use-this-m","canonical_anchor":"new-consent-prompt-lets-claude-cloud-sessions-use-this-m","heading":"Cloud sessions can use this machine's MCP servers after you agree","tier":"notice","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-consent-prompt-lets-claude-cloud-sessions-use-this-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sessions can use this machine's MCP servers after you agree\n\nSessions started with claude --cloud can call MCP servers on your machine once you allow it, with a new prompt whenever a server's tools change\n\n**Unclear.** Whether a server-side setting also controls this feature was not established.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. A cloud session, started with `--cloud`, runs away from your machine. It can now call MCP servers configured on your machine, through that machine, if you allow it. The `device-mcp-consent.json` and `device-mcp-snapshot.json` state files that were already reserved are now used for this.\n\n- Consent: a dialog asks \"Let cloud sessions use this machine's MCP servers?\" with \"Yes, offer this machine's MCP servers\", \"No, keep them to this machine\" and \"Not now\". Focus starts on \"Not now\", and nothing is offered until you allow it. Your answer is saved in `device-mcp-consent.json`, tied to the machine's hostname and to the terms it was given under.\n\n- Local control: the servers keep running on your machine with their saved logins, and your machine's allow, deny and ask rules still decide each call.\n\n- Which servers: only stdio, http, sse and ws servers are offered. sdk, IDE and claudeai-proxy servers are left out. Servers deployed by an administrator are never offered, and servers defined by a project are not offered yet.\n\n- Tool changes: the tools each server listed are saved in `device-mcp-snapshot.json`. If a server's tools change after you approved it, it is held back until you approve again. The prompt says \"An MCP server on this machine changed its tools\" or \"MCP servers on this machine changed their tools\".\n\n- Tools can be dropped for name clashes, deny rules, your organization's permission limit, name length, definition size, schema depth, or limits on how many tools and how much data are announced. Enterprise and managed settings take priority, and dropped tools are listed under \"Not offered to the cloud session:\".\n\n- If a call fails, the error says clearly whether the tool did not run or may have run.\n\nThe flag `tengu_device_mcp_serving` has not been read.\n\n**Why**\n\nA cloud session can reach tools and logins that live only on your laptop. The consent and re-approval prompts, and your local permission rules, decide what it can use.\n\n- Area: Remote Tools\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 5\/5"}