{"version":"2.1.296","anchor":"auth-needed-prompt-for-remote-sessions-without-oauth","canonical_anchor":"auth-needed-prompt-for-remote-sessions-without-oauth","heading":"Remote sessions give accurate sign-in advice for MCP servers","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/auth-needed-prompt-for-remote-sessions-without-oauth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Remote sessions give accurate sign-in advice for MCP servers\n\nIn remote sessions, Claude now explains that claude.ai connectors are authorised in connector settings and other servers can't be signed into there\n\n**What**\n\nMCP (Model Context Protocol) servers are add-ons that give Claude extra tools, and some need you to sign in. When one does, Claude Code tells the model how to help you.\n\nThat guidance has a new version for remote sessions, which are sessions where `CLAUDE_CODE_REMOTE` is set. There it says:\n\n- claude.ai connectors are authorised through connector settings.\n\n- Other servers cannot be signed in to from that session.\n\nOutside remote sessions, the guidance still points to `claude mcp` or `\/mcp`.\n\n**Why**\n\nClaude stops telling people in remote sessions to run `\/mcp`, which does not help them sign in there.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}