{"version":"2.1.302","anchor":"mcp-auth-guidance-wording-adapts-to-claudeai-connectors","canonical_anchor":"mcp-auth-guidance-wording-adapts-to-claudeai-connectors","heading":"MCP sign-in and rejected-credential messages adapt to where Claude Code runs","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/mcp-auth-guidance-wording-adapts-to-claudeai-connectors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### MCP sign-in and rejected-credential messages adapt to where Claude Code runs\n\nMCP authentication messages now come from shared helpers and can say to start a new task or chat instead of pointing to \/mcp\n\n**What**\n\nMCP servers are outside tools that Claude Code connects to. When one needs you to sign in, or turns down the credentials it was given, Claude Code shows a message. These messages changed:\n\n- The messages for a rejected `headersHelper` credential (a command you configure to produce login headers) and for a rejected Authorization header in a server's config now come from shared helpers, `helperRejected` and `headerRejected`, instead of being written in place. The old wording told you to check the helper, or update the header, and then run \/mcp to reconnect. The new wording was not visible in the findings.\n\n- When a particular check is true, MCP messages leave out \/mcp and tell you to start a new task or chat instead.\n\n- The reminder Claude receives when MCP servers need sign-in now chooses its wording by whether those servers are claude.ai connectors. In some cases it tells Claude to explain the step \"without naming a command or settings page\".\n\n**Why**\n\nWhere \/mcp cannot be run, advice to run it is a dead end, and these messages now give a step you can take instead. The exact wording you see may differ from earlier versions.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}