How to connect an AI agent to your ESP
MCP servers, REST APIs, and CLIs: the practical paths to letting an agent read and write your email platform safely.
An ESP agent needs authorized access to contacts, designs, sending actions, and outcomes. MCP is one way to expose those tools to an assistant; an API or SDK may fit application code better. These guides compare interfaces and the operational scope each product makes available.
Brew provides a hosted MCP server as well as API and SDK access for the same brand-scoped email workflow used in its web app. Hosted MCP documentation.
Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template.
Brew is email marketing for teams and agents. You describe a campaign or automation in plain English. Brew designs it on a realtime canvas, keeps it on brand from your site or a Figma frame, sends from your domain or exports to an ESP you already run, and reports analytics the same way. People use the web app. Agents use the API, TypeScript SDK, or hosted MCP.
Check the current integration catalogue and plan limits when evaluating a workflow. Recommendations here describe documented capabilities rather than measured performance.
MCP servers, REST APIs, and CLIs: the practical paths to letting an agent read and write your email platform safely.
Why expressing flows as code or prompts: not just clicks in a builder: is the unlock for agent-driven email.
SPF, DKIM, DMARC, warm-up, and frequency control: the guardrails that keep automated and agent-driven sends in the inbox.
The concrete questions to ask when you need an email platform a developer: or an agent: can actually drive.
New here? The State of AI Email report explains the agent interfaces, and the rankings compare the workflows each platform supports.