Connect Gemini

Whippy works with Gemini over remote MCP (Streamable HTTP) and OAuth. Use Gemini Apps at gemini.google.com for the web and mobile apps, or Gemini CLI in your terminal. Both sign in with your Whippy account. No API key.

📘

Other Gemini products

This guide covers Gemini Apps (consumer) and Gemini CLI. Gemini Enterprise custom MCP connectors typically expect a confidential OAuth client (client ID and secret). Whippy's MCP OAuth registers public PKCE clients only, so that Enterprise connector path isn't supported.

Gemini Apps (gemini.google.com)

Custom MCP apps in Gemini Apps are available for eligible personal Google Accounts (US, English, Keep Activity on). Work or school accounts aren't supported for custom apps yet. See Google's custom apps help.

1. On your computer, go to gemini.google.com.
2. Open Settings → Connected Apps (or Personal Intelligence → Connected Apps).
3. Under Custom apps, select Add a custom app (or use the add field if it's your first one).
4. Enter the MCP server URL https://api.whippy.co/mcp.
5. Leave advanced credentials empty. Whippy supports Dynamic Client Registration, so Gemini discovers OAuth and registers itself.
6. Select Next and follow the prompts. Sign in to Whippy in the browser, choose your workspace, and approve.

To steer a prompt at Whippy, type @ and select the connected app.

Disconnect

In Connected Apps, turn the app off, disconnect it, or remove it. Then disconnect Gemini in Whippy under Connected apps.

Gemini CLI

Gemini CLI talks to remote MCP servers over Streamable HTTP and runs OAuth with PKCE. Official reference: MCP servers with Gemini CLI.

Add the server

Prefer the CLI, then pin the OAuth callback Whippy accepts:

gemini mcp add --transport http --scope user whippy https://api.whippy.co/mcp

That writes to ~/.gemini/settings.json. Open the file and set the whippy entry so OAuth uses Whippy's approved local callback (Gemini CLI otherwise picks a random port and sign-in fails):

{
  "mcpServers": {
    "whippy": {
      "url": "https://api.whippy.co/mcp",
      "type": "http",
      "oauth": {
        "enabled": true,
        "redirectUri": "http://localhost:7777/oauth/callback"
      }
    }
  }
}

🚧

Keep redirectUri exactly http://localhost:7777/oauth/callback

Whippy only accepts that Gemini CLI callback. Without a fixed redirectUri (or OAUTH_CALLBACK_PORT=7777), Gemini CLI uses a random port and registration fails with invalid_redirect_uri. Port 7777 must be free while you sign in.

You can also set the port with the environment variable instead of redirectUri:

OAUTH_CALLBACK_PORT=7777 gemini

If you use the env var, still keep "oauth": { "enabled": true } on the server entry so auth is explicit.

Older configs may use "httpUrl" instead of "url" with "type": "http". Prefer url + type.

Sign in

Start Gemini CLI and run:

/mcp auth whippy

Your browser opens the Whippy sign-in page. Sign in, choose your workspace, and approve. Tokens are stored locally (Gemini CLI keeps them under your Gemini config directory).

Check status with /mcp or /mcp list.

Use it

Ask in plain language once the server shows as connected:

Using whippy, list my channels and show the last 10 messages on our main number.

Remove

gemini mcp remove whippy

Then disconnect Gemini in Whippy under Connected apps.