Unitpost/Guides

Gemini CLI

Prefer the OAuth browser approval. If your setup needs static config, paste the key block instead.

What are the connection details?

Server URLhttps://mcp.unitpost.com/mcp
TransportStreamable HTTP
Auth (recommended)OAuth 2.1 — add the URL, approve in the browser(scopes match API capabilities; tokens refresh automatically)
Auth (legacy)Authorization: Bearer pk_live_YOUR_KEY(workspace API key from Settings → API keys; for clients that can only paste a key)
Toolsone per API operation (email_send, email_campaigns_send, …)

How do I connect Gemini CLI?

  1. Connect with OAuth (recommended)

    Add this block to `~/.gemini/settings.json` (no headers — Gemini discovers OAuth from the 401). No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically.

    JSON
    {
  "mcpServers": {
    "unitpost": {
      "httpUrl": "https://mcp.unitpost.com/mcp"
    }
  }
}

  2. Verify

    Restart the Gemini CLI and run /mcp. unitpost should list its tools. If it shows as needing authentication, run /mcp auth unitpost — the browser opens for approval, and tokens refresh automatically after that.

  3. Send a test

    Ask Gemini to send an email from a verified domain and confirm it in Unitpost Activity.

No browser on this machine? For headless setups, CI, SSH, or clients that can only paste a key, use the API-key setup instead.