Custom MCP Connector OAuth Tokens Fail to Persist Across Sessions in Claude Code

What this error means

[BUG] Custom MCP connector OAuth tokens fail to persist — quarri MCP server requires /exit then claude mcp list workaround is a Claude Code failure pattern reported for developers trying to fix claude code failing to persist oauth tokens for custom mcp connectors across sessions, forcing manual restart via /exit and claude mcp list. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Source: https://github.com/anthropics/claude-code/issues/52565 (April 23, 2026). Recently reported bug — OAuth tokens not surviving session restarts. Workaround: /exit then claude mcp list. Directly affects paid Claude Code users with custom MCP integrations. Category: AI Coding Tools per mapping rules.

Common causes

• Source: https://github.com/anthropics/claude-code/issues/52565 (April 23, 2026). Recently reported bug — OAuth tokens not surviving session restarts. Workaround: /exit then claude mcp list. Directly affects paid Claude Code users with custom MCP integrations. Category: AI Coding Tools per mapping rules.

Quick fixes

1. Confirm the exact error signature matches [BUG] Custom MCP connector OAuth tokens fail to persist — quarri MCP server requires /exit then claude mcp list workaround.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/52565

Evidence note: Source: https://github.com/anthropics/claude-code/issues/52565 (April 23, 2026). Recently reported bug — OAuth tokens not surviving session restarts. Workaround: /exit then claude mcp list. Directly affects paid Claude Code users with custom MCP integrations. Category: AI Coding Tools per mapping rules.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact [BUG] Custom MCP connector OAuth tokens fail to persist — quarri MCP server requires /exit then claude mcp list workaround text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without [BUG] Custom MCP connector OAuth tokens fail to persist — quarri MCP server requires /exit then claude mcp list workaround.