Gemini CLI
Paste one JSON block into Gemini settings, restart, run `/mcp`.
What are the connection details?
| Server URL | https://mcp.unitpost.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Auth header | Authorization: Bearer pk_live_YOUR_KEY(production key from www.unitpost.com) |
| Tools | one per API operation (emails_send, campaigns_send, …) |
How do I connect Gemini CLI?
Create a production API key
Open https://www.unitpost.com → Settings → API keys → create a scoped key. Copy the full
pk_live_…value (shown once). In every snippet below, replacepk_live_YOUR_KEYwith 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.Open Gemini settings
Edit `~/.gemini/settings.json` (user-level) or `.gemini/settings.json` (project).
Paste this server block
Under
mcpServers, addunitpost. Replacepk_live_YOUR_KEY— keepBearer.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:sendforemails_send). Prefer a revocable key dedicated to the agent.Verify
Restart the Gemini CLI and run
/mcp. unitpost should list its tools.Send a test
Ask Gemini to send an email from a verified domain and confirm it in Unitpost Activity.