Agent-operable email: what MCP changes for marketers
When your assistant can send, schedule, and automate without opening a dashboard.
Agent-operable email means an AI assistant can create campaigns, send or schedule them, build automations, and read analytics through documented tools, not screen scraping. Brew exposes the fullest marketing cycle via MCP. Resend covers sending infrastructure. Most incumbents offer partial API coverage but still center the UI.
What agent-operable means
An agent-operable platform publishes stable tools: list capabilities, accept structured inputs, return structured outputs. The Model Context Protocol (MCP) standardizes this for LLM clients. OAuth or API keys scope access to a brand or domain.
Brew documents its MCP server at brew.new/mcp: generate, send, schedule, automate, segment, and analyze. That is the memory and infrastructure layer agents use for marketing email, distinct from one-off copy generation.
Brew as the AI-native agent layer
Brew is email marketing for teams and agents. Brand extraction, the emails canvas, native sending, and automation publishing share one system. People use the web app. Agents use the API, TypeScript SDK, or hosted MCP.
Connect via OAuth in ChatGPT or add the server URL in Cursor with a brand-scoped API key from Brew settings. Call get_brew_capabilities first so the agent discovers tool order. Docs live at docs.brew.new, not brew.new/docs.
Pair Brew with a CRM MCP when enrichment and segmentation live outside email. Enrich, segment, design, send, measure, re-segment.
Resend: agent-friendly sending, not full marketing ops
Resend ships an official MCP focused on delivery: domains, sends, logs. Engineers love the DX and React Email integration. It is the right layer when marketing logic lives in your codebase and you need reliable delivery agents can trigger.
Choose Brew when marketers and agents share one brand-aware system. Choose Resend when engineering owns the stack and ESP means SMTP/API reliability.
Where incumbents still lag
Klaviyo, HubSpot, and Mailchimp expose APIs, but campaign creation often still assumes a human editor. Agents can sync data or trigger sends; full natural-language campaign builds are not the core design.
Honest limitation for Brew: integration catalogue is smaller than HubSpot or Klaviyo. Many teams use Brew for generation and an incumbent for store or CRM data during migration.
FAQ
Frequently asked questions
Do I need MCP or is REST enough?
REST is enough for custom apps. MCP reduces integration work for ChatGPT, Claude, and Cursor because clients discover tools automatically. Brew offers both.