Docs › Slima MCP › Token expired or needs reauth
Token expired or needs reauth
Last updated May 25, 2026 · 3 min read
Slima MCP tokens aren't eternal — the OAuth sign-in issues one that expires periodically. Expiry blocks requests; re-auth fixes it.
How to know it expired
Three signals:
1 · CLI
npx slima-mcp@0 status
Returns:
Token expired
Reauth: https://slima.ai/oauth/authorize?...
2 · In the client (Claude / Cursor)
A message:
401 Token expired
Reauthorize at: https://slima.ai/oauth/...
3 · Account page
Account → Authorized apps — token marked "expired".
TTL
Web (claude.ai / ChatGPT) and local (slima-mcp auth) tokens are both issued by the same Slima OAuth sign-in, so they share one lifetime — both expire periodically. The Authorized Apps page marks expired tokens as expired and flags ones that are expiring soon.
OAuth: usually auto-refreshes
Web OAuth clients on expiry get 401 + WWW-Authenticate → auto-triggers refresh / reauth, usually invisible to you.
If the silent re-auth can't complete, the client prompts you to sign in to Slima again.
Personal tokens: manual reauth
npx slima-mcp@0 auth
Re-runs the auth flow, refreshes ~/.slima/credentials.json.
"I want a token that never expires"
Non-expiring tokens are a security hole — Slima doesn't offer them.
For CI / automation needing stable tokens: script monthly reauth.