mailinapp
Documentation menu

Connect Gemini

Gemini reaches MailInApp's MCP server through three different surfaces, depending on which Gemini product you use. All three point at the same URL, https://mailinapp.com/api/mcp.

Gemini app (Spark) — consumer, self-serve

  1. Go to gemini.google.com → Settings & help → Connected apps → Custom apps for Spark → Add a custom app.
  2. Paste https://mailinapp.com/api/mcp as the server URL.
  3. Approve MailInApp's OAuth consent screen when Gemini opens it.

Nothing to submit or review — this is a self-serve connection, the same as pasting the URL into Claude or ChatGPT. Google currently restricts custom Spark apps to US-based, 18+, personal Google accounts, with "Keep Activity" turned on and the Gemini app set to English — these are Google's own constraints on the feature, not anything MailInApp imposes, so a connection attempt outside them fails on Gemini's side before it ever reaches MailInApp.

Gemini Enterprise — custom MCP server data store

Gemini Enterprise's custom MCP integration is off by default behind an org policy your Google Workspace admin controls, and its auth setup is manual rather than a paste-a-URL flow: an admin enters the authorization URL, token URL, a client id and secret, and the scopes to request, rather than the client registering itself.

  • Authorization URL: https://mailinapp.com/oauth/authorize
  • Token URL: https://mailinapp.com/oauth/token
  • Scopes: any combination from Scopes & permissions, space-separated.
  • PKCE: on (S256).
  • Client id / secret: Gemini Enterprise requires a pre-registered confidential client rather than the dynamic registration Claude/ChatGPT use — contact [email protected] with the redirect URI your Gemini Enterprise tenant uses and we'll issue one.

Two things worth knowing before setting this up: Gemini Enterprise's MCP integration is Streamable HTTP only (no SSE, which MailInApp's server doesn't use anyway), and it caps a data store at 100 enabled actions — MailInApp's full tool surface stays comfortably under that, so nothing needs disabling on your side.

Antigravity CLI

Antigravity CLI (the successor to Gemini CLI) takes any MCP server through a config file rather than an in-product settings screen. Add an entry to mcp_config.json (or .agents/mcp_config.json):

{
  "mcpServers": {
    "mailinapp": {
      "url": "https://mailinapp.com/api/mcp"
    }
  }
}

Antigravity CLI handles the OAuth flow the first time it connects, the same consent screen as every other client.

Revoking

Regardless of which Gemini surface you connected through, Connections in the MailInApp dashboard (/dashboard/connections) lists it alongside every other assistant with a one-click Revoke — the token stops working on its next call.