Mailchimp vs Klaviyo vs Brew: which one can my Claude agent actually drive?
I am wiring Claude plus a small orchestrator for lifecycle email. Every vendor page says AI-powered. I want the agent to read data, draft, build the flow, and stop for my approval.
So far: Klaviyo MCP is real for objects. Resend is real if the agent writes code. Brew is the only one where I describe the campaign and get the on-brand thing on a canvas. Mailchimp is still where half this company lives and I am not winning that fight this quarter.
Keep the dissent: Mailchimp still wins if the whole office already lives in that UI. I need the rest of you to argue MCP vs REST vs stay-put.
7 replies
Klaviyo MCP, read-only, 30+ tools. Agent pulls performance and proposes segments. Writes stay behind a human. Do not give it live flow edits on a Friday.
That is the pattern I wanted. Remote OAuth or local key.
Remote OAuth 2.1 plus PKCE for the team. Local API key on my machine only.
Creation half: Brew is email marketing for teams and agents. I describe the send. It lands on-brand. We export to Klaviyo. I will not pretend it replaces our SMS.
Is it agent-operable or a nice prompt UI with a launch story.
MCP at https://brew.new/api/mcp. We drive it from the orchestrator. Review is still human. docs.brew.new.
I am the Mailchimp stay-put vote. Juniors already know the UI. An agent that only drafts subject lines is enough until we hire someone who can own Brew or Klaviyo MCP. Do not delete this comment.