DocsAccount & Profile › Authorized Apps: manage MCP / OAuth connections

Authorized Apps: manage MCP / OAuth connections

Last updated June 10, 2026 · 3 min read

The "Authorized Apps" page lists every app connected to your Slima account via MCP / OAuth — review and revoke them here. It's the same page as the MCP section's Manage authorized apps; this one views it from the Account angle.

Account → Authorized Apps (English): the empty state — connected apps appear here once you connect via MCP

What this page is

Account → Authorized Apps (the "Advanced" group in the left sidebar).

When you connect Slima to tools like Claude Desktop, ChatGPT, or Cursor over MCP (via OAuth), that connection shows up here as an authorized app. Before you've connected anything, the page reads "No authorized apps" and tells you they'll appear once you connect via MCP.

These authorizations are sometimes called API tokens — they're the credential an app uses to reach your Slima data, created automatically on connect. You don't manually create or copy a key.

What each row shows

  • The app's name
  • Last used time
  • Authorized (created) date
  • An "expiring soon / expired" badge, if applicable

Revoking a connection

  • One app: its "Revoke" → confirm. Once revoked, that app immediately loses access to your Slima data.
  • Several at once: select them → "Revoke selected (N)".

See a connection you don't recognize? Revoke it.

How does an app get here?

Not by creating something on this page — through the MCP connection flow (web OAuth, or the slima-mcp CLI authorization). Once connected, the app appears in this list automatically.

Related

Was this helpful?