{"version":"2.1.323","anchor":"new-connector-sign-in-guidance-string","canonical_anchor":"new-connector-sign-in-guidance-string","heading":"New guidance when a connected server needs another way to sign in","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-connector-sign-in-guidance-string","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### New guidance when a connected server needs another way to sign in\n\nA new message explains that another sign-in method needs a claude.ai connector, and how to set that up\n\n**What**\n\nClaude Code can connect to MCP servers, which are outside tools and services Claude can use. Some need you to sign in. A connector is one of these services set up on claude.ai. A new message explains that Claude Code can't suggest another way to sign in unless claude.ai offers the service as a connector. It tells you to:\n\n- connect the service on claude.ai,\n\n- optionally have the server's own entry removed,\n\n- start a new session.\n\nA sign-in result Claude Code cannot identify is also no longer counted as a failure when the server is restarted.\n\n**Why**\n\nIf you cannot sign in to a service from Claude Code, this message gives you a way forward.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}