{"version":"2.1.323","anchor":"mcp-tool-triggered-oauth-refuses-when-token-refresh-was-refu","canonical_anchor":"mcp-tool-triggered-oauth-refuses-when-token-refresh-was-refu","heading":"MCP sign-in tells you to reconnect when a token refresh was refused","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-tool-triggered-oauth-refuses-when-token-refresh-was-refu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP sign-in tells you to reconnect when a token refresh was refused\n\nIf an MCP server's last token refresh was refused, Claude Code stops the sign-in attempt and tells you to run `\/mcp reconnect` or `\/mcp`\n\n**What**\n\nAn MCP server is an outside service that gives Claude extra tools. Some of them need you to sign in, and Claude Code keeps that sign-in alive by refreshing a token, a kind of temporary pass.\n\nIf the sign-in server refused the last token refresh for an MCP server, Claude Code no longer tries to sign in again from inside the conversation. It reports that it cannot do so and tells you to run `\/mcp reconnect` or `\/mcp` to fix the connection yourself.\n\n**Why**\n\nWhen sign-in to an MCP server fails this way, you now get a clear next step instead of a failed attempt.\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}