Skip to main content
POST
Revoke an MCP client connection
The organization bot token must have the following scopes:
  • mcp-client-connection:write-high-impact
This endpoint revokes the active OAuth tokens for one member and MCP client in a workspace. Use List MCP client connections to get the client_key. The response gives the number of tokens revoked. The endpoint returns the same not-found response when the member, workspace, or connection does not exist or is outside the organization. Revoking tokens disconnects the member, but does not prevent them from connecting the client again if workspace policy allows it. To control which MCP clients members can connect, see Admin controls for Notion MCP.

Enterprise-managed access

If your organization uses enterprise-managed connections, you can deny a member’s enterprise-managed access to revoke their current tokens and prevent them from connecting again through enterprise-managed authentication. This setting applies to the member and workspace, not only to the client identified by client_key.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Notion-Version
enum<string>
required

The Admin API version to use for this request.

Available options:
2026-06-01

Body

application/json
client_key
string
required

Stable client key returned by the list endpoint.

user_id
string<uuid>
required
workspace_id
string<uuid>
required

Response

revoked_token_count
number
required

Number of active tokens revoked.