{"version":"2.1.304","anchor":"cloud-mcp-offer-gains-a-not-now-answer-that-re-asks-when-a","canonical_anchor":"cloud-mcp-offer-gains-a-not-now-answer-that-re-asks-when-a","heading":"Sharing MCP servers with cloud sessions now has a \"Not now\" answer","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/cloud-mcp-offer-gains-a-not-now-answer-that-re-asks-when-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sharing MCP servers with cloud sessions now has a \"Not now\" answer\n\nThe prompt offering your MCP servers to claude --cloud sessions adds \"Not now\", which asks again once you add an MCP server\n\n**What**\n\nMCP servers are add-on connections that give Claude Code extra tools. `claude --cloud` starts a session that runs in the cloud instead of on your machine. Claude Code asks whether to offer this machine's MCP servers to those cloud sessions.\n\nThat question now has a third answer:\n\n- Yes: saved for this machine.\n\n- No: saved for this machine.\n\n- Not now: you are asked again once you add an MCP server.\n\nThe notice wording also changes depending on whether you chose Not now.\n\n**Why**\n\nYou can put off the decision without it being saved as a final no.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}