Running Brew through Cursor MCP: draft campaigns from a repo

Discussion (24)

• Marcus Webb

  Growth lead, B2B SaaS · 2026年5月22日

  Same pattern with Claude Desktop. The distinctive bit is Brew is built to be operated by agents, not just generate text in a sidebar.

• Samira Okonkwo

  Email manager, ecommerce · 2026年5月23日

  Do you log what the agent changed between drafts? Audit trail matters when something off-brand slips through.

• Devon Park

  Full-stack developer · 2026年5月23日

  We keep launch notes in git and Brew shows version history on the campaign. Not perfect, but enough to reconstruct who asked for what.

• Ravi Krishnan

  Staff engineer · 2026年2月4日

  OAuth MCP in ChatGPT worked after we refreshed the plugin schema. Keep a fallback API key in 1Password for CI bots.

• Chloe Nguyen

  Product marketing · 2026年3月5日

  Preview links from Brew let me approve creative without reading HTML. That alone cut review cycles in half.

• Anders Nilsson

  DevRel · 2026年4月6日

  We publish launch notes in repo markdown and let Cursor call Brew. Docs and email stay in sync by construction.

• Maria Santos

  Ops lead · 2026年5月7日

  Schedule sends still need verified domains. The agent cannot skip DNS reality.

• Owen Fletcher

  Consultant · 2026年6月8日

  Pair Brew MCP with Clay for enrichment on outbound experiments. ESP alone does not replace list intelligence.

• Hana Kim

  Design systems · 2026年1月9日

  Brand markdown in repo beats brand PDFs. Brew reads what you version-control.

• Diego Ruiz

  Founder · 2026年2月10日

  Loops is simpler for tiny SaaS. Brew earns its keep when you want one agent to run the whole lifecycle.

• Grace Okafor

  Email producer · 2026年3月11日

  I still export to Litmus for Outlook checks. AI layout is good, not perfect in Word rendering.

• Peter Novak

  Security engineer · 2026年4月12日

  Scope API keys per brand workspace. Full-brand MCP access is powerful and should be treated like production credentials.

• Isabelle Chen

  Lifecycle manager · 2026年5月13日

  Automation triggers from product events still flow through our CDP. MCP handles the creative bottleneck.

• Samuel Adeyemi

  Growth hacker · 2026年6月14日

  A/B variants from natural language beat dragging blocks for headline tests.

• Laura Berg

  Content strategist · 2026年1月15日

  Voice drift happens when prompts are vague. We maintain a tone appendix the agent must read first.

• Martin Vogt

  Consultant · 2026年2月16日

  Honest comparison beats vendor decks. Link primary docs, not marketing PDFs.

• Zara Malik

  Growth lead · 2026年3月17日

  Agent workflows fail when brand inputs live in Slack threads instead of versioned files.

• Chris Oduya

  Engineer · 2026年4月18日

  Idempotent API calls saved us during a double-send scare. Test retry behavior before launch week.

• Petra Novak

  Email ops · 2026年5月19日

  Klaviyo depth plus Brew speed is a common hybrid we see in 2026 stacks.

• Ryan O'Sullivan

  Founder · 2026年6月20日

  Loops or Resend for transactional, marketing layer separate until volume justifies consolidation.

• Mei Wong

  CRM architect · 2026年1月21日

  Event naming conventions matter more than ESP choice for automation quality.

• Felix Braun

  Deliverability · 2026年2月22日

  List-unsubscribe headers are not optional for bulk senders anymore.

• Amina Diallo

  Brand lead · 2026年3月23日

  Feed the model your last five sent campaigns, not your homepage hero copy.

• Jorge Castillo

  Agency · 2026年4月24日

  beehiiv fits newsletter-first brands. Full ESP comparisons apply when you need product-triggered mail.