Get a send

Get a send

Reads one campaign or automation send's current status, delivery accounting and lifetime engagement stats.

Note: Use the sendId returned by send-email. MCP takes report:{kind:"sends",sendId}. Queued is not delivered; inspect delivery accounting and recipient events before recording delivery. Stop polling when terminal or your execution window ends.

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

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 sends get.

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: GET /v1/sends/{sendId}
• 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.