Gemini CLI

Paste one JSON block into Gemini settings, restart, run `/mcp`.

What are the connection details?

Server URLhttps://mcp.unitpost.com/mcp
TransportStreamable HTTP
Auth headerAuthorization: Bearer pk_live_YOUR_KEY(production key from www.unitpost.com)
Toolsone per API operation (emails_send, campaigns_send, …)

How do I connect Gemini CLI?

  1. Create a production API key

    Open https://www.unitpost.comSettings → API keys → create a scoped key. Copy the full pk_live_… value (shown once). In every snippet below, replace pk_live_YOUR_KEY with that value.

    Must be production. Keys from unitpost.dev only work on the dev API. This MCP URL is production (mcp.unitpost.com) — a .dev key returns 401 Invalid API key on tool calls even if the server appears connected.

  2. Open Gemini settings

    Edit `~/.gemini/settings.json` (user-level) or `.gemini/settings.json` (project).

  3. Paste this server block

    Under mcpServers, add unitpost. Replace pk_live_YOUR_KEY — keep Bearer .

    JSON
    {
      "mcpServers": {
        "unitpost": {
          "httpUrl": "https://mcp.unitpost.com/mcp",
          "headers": {
            "Authorization": "Bearer pk_live_YOUR_KEY"
          }
        }
      }
    }

    Grant only the scopes the agent needs (e.g. emails:send for emails_send). Prefer a revocable key dedicated to the agent.

  4. Verify

    Restart the Gemini CLI and run /mcp. unitpost should list its tools.

  5. Send a test

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