Disconnect an app

See which AI assistants can use your Whippy account, and revoke their access.

Every assistant you connect to the Whippy MCP server appears on your Connected apps page. Disconnecting an app stops it from using your Whippy account right away.

See your connected apps

Go to app.whippy.co/settings/connected-apps, or open Settings in Whippy and select Connected apps.

The table lists each app you authorized in the current workspace, the scopes it holds, and when it was registered. It only shows your own connections, not your teammates'.

Disconnect an app

  1. On Connected apps, find the app.
  2. Open the row's action menu and select Disconnect.
  3. Select Disconnect again to confirm.

Whippy revokes the app's access tokens and refresh tokens for you in this workspace. The app's next request fails with 401, and it has to send you through sign-in again to reconnect.

Disconnecting in Whippy doesn't remove the server from the assistant's settings. Remove it there too if you don't plan to reconnect.

Client credentials

Some connectors cannot use Dynamic Client Registration. They ask for a client ID and a client secret. An organization admin creates those under Client credentials on this page, then pastes them into the connector.

The same form covers Gemini Enterprise, Microsoft Copilot Studio when it asks for a secret, and any other https OAuth callback. Choose the matching preset, or Another OAuth client, and paste the callback the connector shows. Whippy shows the secret once. Deleting a credential revokes its tokens.

Gemini Apps, Gemini CLI, Claude, and Copilot Studio Dynamic discovery do not use this section. Those apps appear in the table above after someone signs in.

When access ends automatically

  • A user is disabled. Whippy disconnects every app that user connected in the workspace.
  • A role changes. Tokens keep working, but each tool call is checked against the user's current role, so lost permissions take effect on the next call.

Did this page help you?