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.

Check it works

Ask the agent to call get_usage. It is read-only, it sends nothing, and it answers with your plan, this month's quota and the capacity limits. If you get JSON back, the install is fine.

What it can do once connected

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