What you can see
Each connected app shows four pieces of information:| Column | What it means |
|---|---|
| Application | The MCP client name and icon (Claude, Cursor, VS Code, etc.) |
| Permissions | OAuth scopes granted — hover to see the full list |
| Status | Active if the token is valid; Inactive if it has expired or been revoked |
| Authorized | The date you approved the connection |
Revoking access
Open Connections
Open the actions menu
Locate the app and click the three-dot menu on the right. Select Revoke Access.
Revoking one client does not affect others. Each MCP client registers independently — Claude,
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.
Get started with MCP
Connect Claude, 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