Connect Grok

Grok on the web

Individual Grok users can add custom connectors. On Grok Business or Enterprise, a team admin may need to provision the connector for the team first.

1. Go to grok.com/connectors, select New Connector, then Custom.
2. Name it Whippy and enter the server URL https://api.whippy.co/mcp.
3. Select Add Connector. Grok opens the Whippy sign-in page in a popup. Sign in, choose your workspace, and approve. Allow the popup if your browser blocks it.
4. Open the connector under Plugins → Connectors and turn on the tools you want Grok to use.

If Grok asks for a client ID

Grok usually registers itself. If it shows an OAuth Credentials Required form instead, register Grok with Whippy once:

curl -X POST https://api.whippy.co/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Grok",
    "redirect_uris": ["https://grok.com/connectors-oauth-exchange-code/"]
  }'

Paste the client_id from the response into the form. Leave Client Secret and Scopes empty, keep the discovered endpoints, and choose the PKCE-only token auth method (none).

Grok Build (CLI)

grok mcp add --transport http whippy https://api.whippy.co/mcp

Grok Build opens the Whippy sign-in page the first time it uses the server. If it doesn't, run /mcps in a Grok Build session, select whippy, and press i. Run grok mcp doctor whippy to check the connection.

📘

If the CLI sign-in fails

If sign-in fails with invalid_redirect_uri, Grok Build is using a callback Whippy doesn't accept yet. Connect through Grok on the web instead, and send the callback URL from the error to [email protected].

Remove

Remove the connector in Grok (or run grok mcp remove whippy), then disconnect Grok in Whippy under Connected apps.