Slima MCP

Manage authorized apps

قراءة 4 دقيقة

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

Slima Authorized Apps page: MCP / OAuth connection management

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: typically 30 days, auto-reauthed when expired
  • 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

Each token has a "last 7 days API call count" chart.

A token with unexpected high usage = possible leak. Revoke immediately.

See: Privacy + data safety

Token quota per account

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

Related

Was this helpful?