Postmark vs Brevo
Postmark MCP and Brevo MCP are both official servers from their respective providers, but they sit at opposite ends of the platform spectrum. Postmark's server is deliberately minimal: four tools cover sending a plain or HTML email with sendEmail, sending a templated message with sendEmailWithTemplate, listing account templates with listTemplates, and reading delivery stats with getDeliveryStats. Brevo's server is a gateway to a full marketing and CRM platform, with tools for email_campaign_management, transac_templates, sms_campaigns, whatsapp_campaigns, contacts, lists, segments, attributes, groups, folders, contact_import_export, campaign_analytics, companies, deals, pipelines, notes, tasks, senders, domains, ips, users, processes, and webhooks_management. Postmark runs locally over stdio; Brevo is a hosted remote server. The choice is straightforward: a tight, transactional-email path versus a multi-channel marketing and CRM platform.
How they compare
| Dimension | Postmark | Brevo |
|---|---|---|
| Tool surface | Four tools: sendEmail, sendEmailWithTemplate, listTemplates, and getDeliveryStats. Intentionally minimal and focused. | Over 25 tool groups covering email, SMS, WhatsApp, CRM, contacts, analytics, domains, and account management. |
| Sending scope | Transactional email only: plain or HTML messages and template-based sends against a Postmark server token and message stream. | Email campaigns, transactional templates, SMS campaigns, and WhatsApp campaigns, across multiple sender domains and dedicated IPs. |
| Delivery visibility | getDeliveryStats returns send, open, and click metrics from the Postmark account. No per-message querying beyond that. | campaign_analytics provides performance and reporting across campaigns. Webhook configuration with webhooks_management enables event-driven delivery monitoring. |
| CRM and audience management | None. The server has no contact, list, segment, or CRM tools. | contacts, lists, segments, attributes, groups, and contact_import_export manage the audience; companies, deals, pipelines, notes, and tasks cover CRM. |
| Deployment | Runs locally over stdio via node index.js (also on npm as @activecampaign/postmark-mcp); requires POSTMARK_SERVER_TOKEN, DEFAULT_SENDER_EMAIL, and DEFAULT_MESSAGE_STREAM. | Hosted remote server at https://mcp.brevo.com/v1/brevo/mcp, authenticated with an MCP API key as a bearer token; no local setup needed. |
Verdict
Postmark MCP suits an agent with a single, narrow job: send a transactional or templated email and confirm it landed using getDeliveryStats. Its four-tool surface keeps scope tight and configuration simple, which is its strength for notification and confirmation workflows. Brevo MCP suits an agent that manages the wider picture: running email campaigns alongside SMS and WhatsApp, organizing contacts and segments, tracking deals and tasks in a CRM, and pulling campaign analytics. If the requirement is broader than firing transactional email, Brevo covers it; if it is not, Postmark keeps things simple.
FAQ
- Can Postmark MCP manage contacts or run campaigns?
- No. Postmark MCP has four tools, all focused on sending: sendEmail, sendEmailWithTemplate, listTemplates, and getDeliveryStats. There are no contact, campaign, segment, or CRM tools. For those, Brevo MCP is the right choice.
- Does Brevo MCP support transactional email, not just marketing campaigns?
- Yes. Brevo's server includes transac_templates for transactional email templates alongside the marketing email_campaign_management tools, so both transactional and campaign sends are supported from the same server.