Send email from the Gemini CLI

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

  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 Emails.

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

Search docs and guides

Search the docs and product guides.