Revoke All MCP Connections
Offboarding in one call: revoke every delegated-OAuth connection on an MCP server.
DELETE
Revoke every delegated-OAuth connection on an MCP server
Revokes every connection on this MCP server and returns how many. Each one’s
stored tokens are destroyed rather than flagged.
Archiving the server, or changing its
auth configuration, does the same thing
automatically — the stored tokens were issued for one OAuth app, one set of
scopes and one upstream, so keeping them across a change would mean dialling with
credentials minted under settings nobody can see any more.
Requires the delete capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope and error types.Authorizations
OAuth 2.1 authentication — recommended for new integrations. Access tokens
(kc_ prefix) are minted at the root-host token endpoint
https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>.
Public clients must use PKCE with the authorization_code grant; confidential
clients may use client_credentials. The first-party SDKs and the
knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.
Path Parameters
The MCP server UUID.