Claude Code / AI Coding Tools

[BUG] HTTP MCP OAuth tokens written to macOS Keychain but not loaded at session start — re-auth required every session

Fix Claude Code requiring manual MCP server re-authentication after every session restart, even when OAuth tokens are confirmed present in macOS Keychain Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 22, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 22, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry is a Claude Code failure pattern reported for developers trying to fix claude code requiring manual mcp server re-authentication after every session restart, even when oauth tokens are confirmed present in macos keychain. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Found in anthropics/claude-code#57674 (open, created 2026-05-09). Detailed Keychain-level evidence proves tokens ARE persisted but NOT restored at session launch. Affects all HTTP MCP servers using Codex MCP Credentials service. High commercial value — breaks paid Claude Code Pro/Max workflows daily. Category maps to AI Coding Tools per SKILL rules.

Common causes

Found in anthropics/claude-code#57674 (open, created 2026-05-09). Detailed Keychain-level evidence proves tokens ARE persisted but NOT restored at session launch. Affects all HTTP MCP servers using Codex MCP Credentials service. High commercial value — breaks paid Claude Code Pro/Max workflows daily. Category maps to AI Coding Tools per SKILL rules.

Quick fixes

Confirm the exact error signature matches ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
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

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
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.

Diagnostic flow for this page

Match ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry mean in Claude Code?

! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry indicates the workflow described by "[BUG] HTTP MCP OAuth tokens written to macOS Keychain but not loaded at session start — re-auth required every session" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry?

Check whether this cause matches your environment: Found in anthropics/claude-code#57674 (open, created 2026-05-09). Detailed Keychain-level evidence proves tokens ARE persisted but NOT restored at session launch. Affects all HTTP MCP servers using Codex MCP Credentials service. High commercial value — breaks paid Claude Code Pro/Max workflows daily. Category maps to AI Coding Tools per SKILL rules.

Is the ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry guidance source-backed?

The "[BUG] HTTP MCP OAuth tokens written to macOS Keychain but not loaded at session start — re-auth required every session" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry?

For "[BUG] HTTP MCP OAuth tokens written to macOS Keychain but not loaded at session start — re-auth required every session", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging ! Needs authentication — MCP OAuth token saved in Keychain (Codex MCP Credentials) but not read at startup; runtime stamps mcp-needs-auth-cache.json despite valid keychain entry?

For "[BUG] HTTP MCP OAuth tokens written to macOS Keychain but not loaded at session start — re-auth required every session", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.