List MCP client connections in an organization
MCP client connections
List MCP client connections in an organization
List inbound MCP client connections across an organization.
GET
List MCP client connections in an organization
The organization bot token must have the following scopes:
Filters only match workspaces in the organization that owns the token. Unknown or out-of-organization IDs return no matching results. A
mcp-client-connection:read
is_enterprise_managed and idp_issuer match, so every workspace in a row can be governed the same way. Within a row, created_at is the earliest connection time and last_active_at is the most recent activity time.
Use bracket encoding to filter by one or more members or workspaces:
workspace_ids filter limits both the returned rows and their connection metadata to the selected workspaces; state from an excluded workspace is not folded into a matching row.
The response contains the standard user reference only. For clients in Notion’s trusted registry, client.name and client.type come from that registry. A custom or unregistered client’s name can come from metadata reported by the client and its type is other; use client.key as the stable identifier. idp_issuer is present only for enterprise-managed connections.
This endpoint inventories member-bound OAuth client connections. It does not include direct MCP usage through personal access tokens or workspace-owned internal integrations. Govern personal access tokens with the personal access token endpoints; manage internal integrations in the workspace’s integration settings.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
The Admin API version to use for this request.
Available options:
2026-06-01 Query Parameters
Cursor returned by the previous page.
Number of results to return. Defaults to 100 and cannot exceed 100.
Member IDs to include. Use bracket encoding for multiple values.
Workspace IDs to include. Use bracket encoding for multiple values.