Revoke an assistant connection using a same-origin browser session
/api/mcp/connections/{id}Revoke an assistant connection using a same-origin browser session.
Personal and person-only: only the signed-in person can list or revoke their own assistant connections, in their browser on Assistant connections, with this conversation's organization prefix as . An agent cannot do it for them: these routes accept only the person's own signed-in browser session, and the only other revocation is OAuth token revocation sent by the connected assistant itself with its own token. Do not search for another route; link that page and tell the person which connection to revoke. Revoking stops that assistant's further calls; tasks it already created keep their assignees and running work.
Authorization
Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.
Path parameters
Responses
details names each field that failed.Errors return {"error": "..."}, often with a code and details. See errors and limits.