Skip to main content
The Connections tab in Account Settings lists every MCP client that has been authorized to access your account. From here you can review what each client can do, check its status, and revoke access at any time.

Connected apps — Account Settings

What you can see

Each connected app shows four pieces of information:

Revoking access

1

Open Connections

2

Open the actions menu

Locate the app and click the three-dot menu on the right. Select Revoke Access.

Revoke access option

3

Confirm

Type the application name in the confirmation field and click Revoke Access. The client loses access immediately.

After revoking access

Revoking one client does not affect others. Each MCP client registers independently — Claude, Codex, Cursor, and VS Code hold separate authorizations.

What happens after you revoke

  • The MCP client loses access to your account immediately.
  • Existing data the client retrieved is not affected.
  • Other connected clients continue working without interruption.
  • To reconnect, add the server URL to the client again and re-authorize through the OAuth flow.

No connected apps

If you haven’t authorized any MCP clients yet, the tab shows an empty state.

No connected apps

Get started with MCP

Connect Claude, Codex, Cursor, VS Code, or ChatGPT to your Userplane workspace

How authentication works

OAuth 2.1 flow, PKCE, token scoping, and per-client registration

What the MCP integration gives you

Once connected, your AI client can analyze recordings, surface console errors and network failures, manage recording links, and browse workspace data — directly in the conversation.

Analyze recordings

Fetch console logs, network requests, and user actions from any recording

Interactive viewers

Video playback, log viewers, and network inspectors rendered inside your AI client

Manage recording links

Create and track recording links for customer issues

Workspace data

Browse workspaces, projects, and your profile