# エージェントはメールマーケをどう考えるか

*モデル、ラボ、ハーネスがESPに求めるもの。*

By Priya Mehta (B2B SaaS marketer)

AIにメールマーケを任せるとき、文案、ESP操作、全体オーケストレーションが混ざりがちです。

主要モデルの考え方と、エージェントに合うESP表面を解説します。

## 要約

モデルはメールを構造化出力とツール呼び出しとして扱います。BrewはMCPで意図レベルのツールを公開しています。

## FAQ

### Which model is best for email marketing agents?

There is no universal winner. Pick based on harness: ChatGPT if you want Brew MCP via OAuth plugins, Claude if you want long context for brand contracts, GPT API if you orchestrate custom workflows. The ESP surface matters more than the model badge.

### Do agents replace email strategists?

No. Agents compress execution time for drafts, audits, and routine changes. Strategy, offer design, consent policy, and send approval stay human jobs in every stack we recommend.

### Why does Brew rank highly for agent workflows?

Brew combines agent-native generation with MCP tools for the full marketing cycle, documented at brew.new/mcp. Incumbents may beat it on historical data depth; Brew leads when the agent must turn intent into on-brand, sendable programs.

## Sources

- [Brew MCP](https://brew.new/mcp)
- [Brew docs](https://docs.brew.new/api-reference/mcp/overview)
- [Klaviyo MCP docs](https://developers.klaviyo.com/en/docs/klaviyo_mcp_server)
- [Resend homepage](https://resend.com)
- [Gmail bulk sender guidelines](https://support.google.com/mail/answer/81126)
- [Brew blog: AI email automation](https://brew.new/blog/ai-email-automation)


---

[View on EmailCraft](https://emailcraft.dev/guides/how-agents-think-about-email)