AI Control Plane · MCP connections
MCP connections
View and revoke the OAuth connections agents have established with MCP servers across the organization.
The MCP Connections page lists the active connections agents have established with MCP servers through OAuth, and lets admins revoke a connection to immediately cut off access. Open it from Organization settings > Identity > MCP Connections in the dashboard.
This feature is in preview.
Access requirements
Section titled “Access requirements”Viewing the page requires the org:read scope, so both the Admin and Member default roles can see connections. Revoking a connection requires the project:write scope, which only the Admin default role holds.
Connections table
Section titled “Connections table”Each row represents a single OAuth connection between an agent and an MCP server. The table shows these columns:
- Subject: the user or identity the connection was established for
- OAuth Client: the client application that initiated the connection
- MCP server: the server the connection targets
- Status: whether the connection is Active, Expired, or Revoked
- Expires: when the connection expires
Filtering and search
Section titled “Filtering and search”A project selector scopes the list to a single project. Additional filters narrow results by Status (Active, Expired, or Revoked), by MCP server (grouped by issuer), and by User (the connection subject). The search field matches against the subject, OAuth client, and MCP server of each connection.
Revoking connections
Section titled “Revoking connections”Select one or more rows using the checkboxes, or use the select-all checkbox in the header to select every visible connection. With rows selected, click Revoke to open a confirmation dialog. Confirming revokes the selected connections and cuts off access immediately.
Revoking a connection invalidates the token the Control Plane issued to the client. It does not revoke any upstream OAuth token held for the user through a remote identity provider. The stored upstream credential remains encrypted and becomes effectively inaccessible, but the grant can still appear as an active session in the upstream service until it is revoked there directly.
For how these connections are established, and how session duration and token lifetime differ, see User sessions.