via mcp-remote

Send email from Gemini CLI

Email from Gemini in the terminal, over the bridge.

Remote server, nothing to install · config in ~/.gemini/settings.json

Setup

Bridge stdio to our HTTP endpoint

{
  "mcpServers": {
    "sending": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://sending.dev/api/mcp",
        "--header", "Authorization: Bearer sk_your_api_key"
      ]
    }
  }
}

Create the API key under Settings › API Keys. The plaintext token is shown once, at creation.

The thing that catches people

Gemini CLI · gotcha

`settings.json` holds every other Gemini CLI setting: the block goes merged into the file, not pasted over it. Replacing the file resets the rest of your configuration and nothing says so.

Check it works

`gemini mcp list` shows the server and its connection state.

What it can do once connected

85 tools: send transactional email and campaigns, manage contacts and lists, build and activate automations, run an inbox that receives and replies, and read back why a message never went out. All of it inside verified domains, suppression, idempotency, spend caps and an audit log, enforced on our servers rather than in the prompt.

All 85 tools · MCP docs

Other clients

Claude Code

Send email from the terminal, inside the session you are already in.

Claude Desktop

Give Claude an email stack without pasting a secret anywhere.

claude.ai

The same connector, in the browser.

ChatGPT

Custom connectors, and the API path where a key still works.

Cursor

Email tools in the editor where you are writing the app that sends them.

VS Code

GitHub Copilot with a mailer attached, and the key never committed.