Send an email

Send an email

Queues a design from a verified marketing domain to a saved audience or up to 50 existing subscribed contacts, or sends a QA copy with test:true.

Note: Supply subject and existing subscribed recipients. Use idempotency_key (MCP) or Idempotency-Key (HTTP), reusing it for retries. On confirmation_required, obtain approval and repeat with confirmed:true and the returned confirmation_id. Queued is not delivered.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "brew": { "url": "https://brew.new/api/mcp" } } }

Call the MCP tool send_email.

Server URL: https://brew.new/api/mcp

CLI (official)

Install the command, then confirm it runs.

brew install getbrew/tap/brew-cli
brew-cli --version

Run brew-cli emails send.

Set $BREW_API_KEY in your environment first (get a key: https://brew.new/settings/api).

API (official)

• Base URL: https://brew.new/api
• Endpoint: POST /v1/sends
• Auth: send the header Authorization: Bearer $BREW_API_KEY
• Get a key: https://brew.new/settings/api
• Docs: https://docs.brew.new/api-reference/api/api-introduction

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.