Token expired or needs reauth
Slima MCP tokens aren't eternal — OAuth ~30 days, personal tokens ~90 days. Expiry blocks requests; reauth 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".
TTLs
| Token type | TTL |
|---|---|
| OAuth (Web, e.g. claude.ai) | ~30 days, refresh token available |
| Personal token (stdio) | ~90 days, no refresh |
Exact days may change — see slima.ai/plans.
OAuth: usually auto-refreshes
Web OAuth clients on expiry get 401 + WWW-Authenticate → auto-triggers refresh / reauth, usually invisible to you.
Only when the refresh token also expires do you need a full re-OAuth.
Personal tokens: manual reauth
npx slima-mcp@0 auth
Re-runs the auth flow, refreshes ~/.slima/credentials.json.
Active extension
If you're still using the token, its TTL extends on every successful API call (session-like).
So only long-unused tokens actually expire. Daily-use tokens extend automatically.
"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.
Related
Was this helpful?