{"version":"2.1.222","anchor":"mcp-server-panel-explains-a-rejected-claude-ai-session-token","canonical_anchor":"mcp-server-panel-explains-a-rejected-claude-ai-session-token","heading":"MCP server panel explains a rejected claude.ai session token","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/mcp-server-panel-explains-a-rejected-claude-ai-session-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### MCP server panel explains a rejected claude.ai session token\n\nAn MCP server rejecting your login token now tells you to run \/login and reconnect.\n\n**What**\n\nA connected MCP server whose discovery bearer token was rejected now tells you to re-login instead of showing a generic tools-list failure.\n\n**Details**\n\n- A dedicated Issue line instructs you to run \/login and then reconnect.\n- The generic tools-list error is suppressed in that specific case.\n\n**Evidence**\n\n`claude.ai rejected the session token. Run \/login, then reconnect.`\n\n- Area: MCP\n- Names: `\/login`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}