Claude Code / AI Coding Tools

Token caching causes repeated Claude Code auth failures across sessions

Fix Claude Code MCP server repeatedly failing with revoked refresh token when sharing config between MCP server and Claude Code plugin Includes evidence for Claude Code troubleshooting demand.

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

Category: AI Coding Tools
Error signature: invalid_grant — Refresh token revoked
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 24, 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

invalid_grant — Refresh token revoked is a Claude Code failure pattern reported for developers trying to fix claude code mcp server repeatedly failing with revoked refresh token when sharing config between mcp server and claude code plugin. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #2 on demasir/spotify-set-reorder (2026-05-17). The bundled MCP server caches its refresh token in memory but writes to a different spotify-config.json than what Claude Code plugin reads. Once the token rotates/revokes, the MCP is stuck failing until Claude Code is restarted. Affects developers using Claude Code as their primary coding assistant. Tier 0 GitHub REST API result.

Common causes

GitHub issue #2 on demasir/spotify-set-reorder (2026-05-17). The bundled MCP server caches its refresh token in memory but writes to a different spotify-config.json than what Claude Code plugin reads. Once the token rotates/revokes, the MCP is stuck failing until Claude Code is restarted. Affects developers using Claude Code as their primary coding assistant. Tier 0 GitHub REST API result.

Quick fixes

Confirm the exact error signature matches invalid_grant — Refresh token revoked.
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 invalid_grant — Refresh token revoked 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 invalid_grant — Refresh token revoked mean in Claude Code?

invalid_grant — Refresh token revoked indicates the workflow described by "Token caching causes repeated Claude Code auth failures across sessions" 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 invalid_grant — Refresh token revoked?

Check whether this cause matches your environment: GitHub issue #2 on demasir/spotify-set-reorder (2026-05-17). The bundled MCP server caches its refresh token in memory but writes to a different spotify-config.json than what Claude Code plugin reads. Once the token rotates/revokes, the MCP is stuck failing until Claude Code is restarted. Affects developers using Claude Code as their primary coding assistant. Tier 0 GitHub REST API result.

Is the invalid_grant — Refresh token revoked guidance source-backed?

The "Token caching causes repeated Claude Code auth failures across sessions" 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 invalid_grant — Refresh token revoked?

For "Token caching causes repeated Claude Code auth failures across sessions", 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 invalid_grant — Refresh token revoked?

For "Token caching causes repeated Claude Code auth failures across sessions", 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.