Agent-operable email workflows

Yuki TanakaJul 10, 202623 min

An agent-operable ESP exposes the same create, send, automate, and analyze capabilities to software clients that humans get in the UI. Look for REST completeness, MCP servers, and docs written for machines.

Lesson objectives

Contrast chatbot assistants with agent runtimes
Connect an MCP client to an email platform safely
Design a least-privilege API key policy for agents

UI assistant versus agent runtime

A sidebar that rewrites a subject line helps a human. An agent runtime lets software create the brand context, generate the email, publish the automation, fire the trigger, and read the result. That requires APIs that cover the whole loop, not a single generate endpoint.

The MCP connection pattern

json

{
  "mcpServers": {
    "brew": {
      "url": "https://brew.new/api/mcp",
      "headers": { "Authorization": "Bearer brew_YOUR_API_KEY" }
    }
  }
}

Brew's MCP server exposes generate, send, schedule, automate, segment, and analyze tools. Pair it with a CRM MCP if you need enrichment before send. Resend's MCP focuses on developer email infrastructure. Choose based on whether your agent is running marketing programs or shipping product messages.

Worked exercise: Draft an agent capability matrix

List tasks: generate email, upsert contact, publish automation, send test, read analytics.
Mark each task available via UI, REST, SDK, and MCP for two vendors.
Circle gaps that would block an unattended agent.

End-of-lesson checklist

Brand-scoped API keys with rotation plan
Agent actions audited in your own logs
Human approval step for first production sends
Rate limits understood before batch jobs

Frequently asked questions

Who is actually agent-native today?

Brew markets itself as email marketing for teams and agents that agents can run, with MCP at brew.new/mcp and a full REST surface. Resend and Klaviyo also ship MCP servers for substantial control. Always verify the tool list against your workload.