Manage authorized apps

Your Slima account may have several clients connected — claude.ai, Cursor, Claude Desktop, Gemini CLI. Account → Authorized apps is the audit + revoke surface.

Open it

Slima Account → Authorized apps

What you see

Per client / token:

• Name: yours (e.g. "Claude Desktop") or auto-detected (e.g. "claude.ai - OAuth")
• Type: OAuth (Web) / Personal token (stdio)
• First connected
• Last used
• Status: active / expired
• Revoke button

Two types

OAuth (Web)

• Source: claude.ai, ChatGPT
• TTL: expires periodically; on expiry the client auto-reauths on next use
• Revoke effect: next use triggers reauth

Personal token (stdio)

• Source: manual / npx slima-mcp@0 auth
• TTL: long-lived (until you revoke)
• Revoke effect: client stops working until a new token is issued

Revoke one

Row ⋯ → Revoke → confirm.

Immediate — next API call returns 401.

Bulk revoke

Top ⋯ → "Revoke all OAuth" / "Revoke all Personal" / "Revoke everything".

Good for:

• New machine, clean up old ones
• Suspected token leak — stop everything immediately
• Cleaning out long-unused clients

Suspicious activity

For each token the page lists its last-used time and status (active / expired).

If a token's last-used time looks wrong (it shows recent use when you haven't used it), or you don't recognise the client at all, it may be a leak — revoke it immediately.

See: Privacy + data safety

Token quota per account

Each plan has a different token limit — see /plans for current numbers.

Related

• Get SLIMA_API_TOKEN
• slima-mcp CLI
• Troubleshoot token expired