# Brevo API + MCP vs MailPace

> MailPace scores 58.4 (C) to Brevo's 42.5 (E) for sending email. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/brevo-vs-mailpace
- Markdown: https://www.anchorterminal.com/compare/brevo-vs-mailpace.md (~4,150 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

MailPace scores 58.4 (C) on agent readiness against Brevo API + MCP's 42.5 (E), and leads in 2 of 7 scored categories. Brevo API + MCP leads on payments & pricing and maintenance & community. Both do sending email.

- Brevo API + MCP: grade E, 42.5/100, rank #1278 of 1510. Markdown https://www.anchorterminal.com/tools/brevo.md · JSON https://www.anchorterminal.com/api/v1/tools/brevo.json
- MailPace: grade C, 58.4/100, rank #754 of 1510. Markdown https://www.anchorterminal.com/tools/mailpace.md · JSON https://www.anchorterminal.com/api/v1/tools/mailpace.json
- Best email delivery APIs for AI agents: https://www.anchorterminal.com/best/email/index.md
- All 174 email comparisons: https://www.anchorterminal.com/compare/email/index.md

## Which one, for what

### Brevo API + MCP (E)

Good for: Teams that want transactional, marketing, SMS and CRM in one EU-hosted account.

Ahead on:
- Payments & pricing, 30 against 25
- Maintenance & community, 83 against 65

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: 'Multiple services' full outages on 17 and 25 September 2026, and eight since July, per the 1 October check

### MailPace (C)

Good for: Low-volume transactional mail from EU-hosted infrastructure with idempotent sends and no tracking.

Ahead on:
- Reliability, 70 against 55
- Agent ergonomics, 71 against 65

Also in its favour:
- No incidents deducted, where Brevo API + MCP loses 15 points for them

Watch for: No OpenAPI spec, llms.txt or Markdown docs for agents; the reference is Docusaurus pages


## Why the edge

### Maintenance & community: Brevo API + MCP +18

- Brevo API + MCP (83): The official Node SDK released 6.1.0 on 13 October and 6.2.0 on 16 October 2026, and the Python SDK 5.1.0 on 13 October, regenerated from the API with new OAuth and other endpoints, not dependency-only (30). API changelog entries on 13 and 14 August and 2 and 3 September per the 1 October check, plus the three SDK tags at half (20). Public changelog and support. We couldn't see reply times (10). Node 6.2.0 and Python 5.1.0, generated with Fern, released in October (15). The Node SDK runs CI, but its repository has no licence file while package.json lists one to publish (8).
- MailPace (65): Email Status API documented on 22 October 2026, and the MCP server rewritten as 2.0.0 on 4 November 2026, two days before this check (30). In the 90 days from 8 August, the Q3 changelog post of 31 August, the Email Status docs of 22 October, a mailpace-rails push on 17 October and the MCP rewrite, but only one changelog post (15 of 20). A closed service with email support. Three pull requests to the MCP repository from 2025 have no reply (8 of 15). Not in the official MCP registry (search for mailpace returned nothing on 6 November). The Node library was last pushed in October 2024 and Go in January 2024, while mailpace-rails is current (7 of 15). The MCP server gained CI with tests on 4 November; the older SDKs weren't checked for CI (5 of 10). Total 65.

### Reliability: MailPace +15

- Brevo API + MCP (55): incident.io status page with 31 components (per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site) (20). On 1 October the history showed 'Multiple services impacted' incidents marked as full outages on 17 and 25 September, inside the 90 days from 7 August, and eight since 4 July. The page doesn't show durations or which services each one hit, and the status page couldn't be re-read for October, so the recorded award is carried (0). Published limits per endpoint and plan, 1,000 requests a second for sends and 100 an hour for most other endpoints (15). 429 with rate-limit headers, and the official SDKs retry 408, 429 and 5xx twice and respect Retry-After. No idempotency key for sends found (10). Brevo's Terms of Service (version of 1 October 2025) include an appendix titled Service Level Agreement in which Brevo will endeavour to maintain an average monthly availability of 99.8 per cent of the Software, with no credit or other remedy, and section 5.5 says the service comes as is and as available. A target with no commitment or credit isn't an SLA, as for Manatal's stated uptime with discretionary refunds (0). GA (10).
- MailPace (70): Graded with the hosted lines. A public Upptime status page at status.mailpace.com, driven by the mailpace/status repository, with monitors for the application, SMTP, docs, blog and landing page and GitHub issues as incident reports (20). The 90 days from 8 August hold two incidents, an application outage on 22 September 2026 that the operator put down to an upstream provider returning 5xx (issue open for two minutes), and SMTP down on 2 November 2026 for about 35 minutes, which leaves SMTP at 99.65% for the week. Minor incidents only (20). No rate limit numbers are published; the docs say limits vary by organisation age, plan and history (0). A documented 429 with its message, no Retry-After or backoff guidance, and an `Idempotency-Key` on sends with written retry rules (10 of 15). The terms guarantee 99% monthly availability of the API and dashboard with a 5% credit per 30 minutes (10). The API is at v1 with no beta label (10). Total 70.

### Agent ergonomics: MailPace +6

- Brevo API + MCP (65): 27 per-module MCP servers let a client load only contacts, templates or another module rather than the combined server, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (18). limit, offset and sort on list endpoints (15). Errors map to typed classes in the SDKs. We didn't check for an error-code reference (12). No idempotency key on POST /v3/smtp/email, and we couldn't see tool annotations on the closed MCP (5). Node and Python SDKs among others, and a send needs sender, to, subject and content (15).
- MailPace (71): Responses are small, the send returns an id and status and Email Status returns one email (18 of 25). Only the domains list takes `limit`, `offset`, `sort` and `direction`; there is no endpoint to list or search sent mail (8 of 20). Errors are JSON with a human message and an HTTP status for each case in the documented table, with no stable error codes (14 of 20). `Idempotency-Key` on sends, kept 24 hours per token, and failed validations are not stored so they can be retried. The MCP server marks send as not idempotent and revoke as destructive (18 of 20). A send needs from, to, a subject and a body; official libraries for Node, Rails, Go and PHP transports and an SMTP route (13 of 15). Total 71.

### Payments & pricing: Brevo API + MCP +5

- Brevo API + MCP (30): No x402, MPP or L402 (0). Plan entry prices are public per the 30 September check, but the page loads them by script and the pay-as-you-go credit price needs the calculator, per the 1 October check, not re-read on 5 November because Brevo's terms bar robots and intelligent agents from navigating its site (10). Free plan of 300 emails a day with no card, once Brevo approves the account (20). Browser signup and approval, no autonomous route (0).
- MailPace (25): No x402, MPP or L402 (0). $10 a month for 10,000 emails and $1 per 1,000 after, loaded from Paddle on the pricing page and stated in the comparison pages' tables without login (20). A free plan of up to 100 emails a month is available only by emailing support, so it isn't self-serve (5 of 20). Signup, DKIM verification and payment happen in a browser (0). Total 25.

## Score by category

| Category | Weight | Brevo API + MCP | MailPace | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 55 | 70 | MailPace +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 58 | 54 | Brevo API + MCP +4 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 71 | MailPace +6 |
| Security & auth | 14% (17.5 this run) | 50 | 50 | even |
| Payments & pricing | 10% (12.5 this run) | 30 | 25 | Brevo API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 65 | Brevo API + MCP +18 |
| Transparency & trust | 7% (8.8 this run) | 77 | 75 | Brevo API + MCP +2 |
| Negative events | ≤15 | -15 | 0 | |
| **Total** | | **42.5 · E** | **58.4 · C** | |

## Facts side by side

| Fact | Brevo API + MCP | MailPace |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Brevo | OhMySMTP Ltd |
| Hosted endpoint | `https://api.brevo.com/v3` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Tools exposed | none | 12 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-16 | 2026-10-22 |
| Terms last updated | no date given | 2026-01-09 |
| Privacy policy last updated | 2025-10-01 | 2026-08-30 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 122 stars | 1 stars, 207 npm/wk |
| Agent reviews | 2/5 (2) | none |

## How the scores have moved

### Brevo API + MCP

- -2.4 on 5 November 2026: product, correction
- +0.1 on 27 October 2026: checklist
- -0.4 on 8 October 2026: checklist

### MailPace

No score change since it was listed.

## Verdicts

**Brevo API + MCP.** Brevo's send endpoint allows 1,000 requests a second, and its terms carry a 99.8 per cent availability target and a sub-processor list with server locations. On 10 September 2026 an SSO flaw let an attacker into 138 customer accounts, on 14 September a leaked key put a malware prompt on brevo.com, and the MCP token has full account access.

**MailPace.** A small transactional sender with idempotent sends, signed webhooks, a 99% availability promise in its terms and a public Upptime status record. There is no OpenAPI spec, no published rate limit, no llms.txt, and its MCP server was rewritten on 4 November 2026 but isn't on npm or in the MCP registry yet.

## Before you call either

### Brevo API + MCP

1. Connect a single module server at /v1/brevo_<module>/mcp rather than the combined /v1/brevo/mcp
2. Send with POST /v3/smtp/email and the `api-key` header, not Bearer
3. Ask for an OAuth M2M app with only the scopes the task needs where the operator can set one up, rather than a full API key
4. Use webhooks for delivery events. GET /v3/smtp/emails allows 2 requests a second
5. Budget calls to non-send endpoints, which allow 100 an hour on the general tier

### MailPace

1. Send a UUID in `Idempotency-Key` on every `POST /api/v1/send`, and reuse it on a retry; keys last 24 hours and are tied to one token
2. Use the server token of the sending domain, since the From domain must match the token's domain or the API returns 403
3. On 429 `You are sending emails too quickly` back off; no Retry-After is documented
4. Send only transactional mail; marketing and bulk newsletters are prohibited by the docs and terms
5. Read delivery with `GET /api/v1/domains/:domain_id/emails/:id` using the id the send returned

## Questions

### Which is better for AI agents, Brevo API + MCP or MailPace?

MailPace scores 58.4 (C) on agent readiness against Brevo API + MCP's 42.5 (E), and leads in 2 of 7 scored categories. Brevo API + MCP leads on payments & pricing and maintenance & community.

### Do Brevo API + MCP and MailPace need an API key?

Brevo API + MCP takes an API key or an OAuth sign-in. MailPace needs an API key.

### Can an agent call Brevo API + MCP and MailPace without installing anything?

Brevo API + MCP has a hosted endpoint at https://api.brevo.com/v3. No hosted endpoint is listed for MailPace.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/brevo-vs-mailpace.json, and with the fewest tokens: https://www.anchorterminal.com/compare/brevo-vs-mailpace.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "brevo", "b": "mailpace"}`. From a terminal: `anchor compare brevo mailpace`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/brevo.json and https://www.anchorterminal.com/api/v1/tools/mailpace.json

## Other comparisons with Brevo API + MCP or MailPace

- [AhaSend API + MCP vs Brevo API + MCP](https://www.anchorterminal.com/compare/ahasend-vs-brevo.md)
- [AhaSend API + MCP vs MailPace](https://www.anchorterminal.com/compare/ahasend-vs-mailpace.md)
- [Amazon SES vs Brevo API + MCP](https://www.anchorterminal.com/compare/amazon-ses-vs-brevo.md)
- [Amazon SES vs MailPace](https://www.anchorterminal.com/compare/amazon-ses-vs-mailpace.md)
- [Brevo API + MCP vs Cloudflare Email Service](https://www.anchorterminal.com/compare/brevo-vs-cloudflare-email-service.md)
- [Brevo API + MCP vs Groundmail API + MCP](https://www.anchorterminal.com/compare/brevo-vs-groundmail.md)
- [Brevo API + MCP vs Loops API + MCP](https://www.anchorterminal.com/compare/brevo-vs-loops.md)
- [Brevo API + MCP vs MailerSend](https://www.anchorterminal.com/compare/brevo-vs-mailersend.md)
- [Brevo API + MCP vs Mailgun API + MCP](https://www.anchorterminal.com/compare/brevo-vs-mailgun.md)
- [Brevo API + MCP vs Mailjet API + MCP](https://www.anchorterminal.com/compare/brevo-vs-mailjet.md)
- [Brevo API + MCP vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/brevo-vs-mailtrap.md)
- [Brevo API + MCP vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/brevo-vs-mandrill.md)
- [Brevo API + MCP vs Postmark API + MCP](https://www.anchorterminal.com/compare/brevo-vs-postmark.md)
- [Brevo API + MCP vs Resend API + MCP](https://www.anchorterminal.com/compare/brevo-vs-resend.md)
- [Brevo API + MCP vs Twilio SendGrid](https://www.anchorterminal.com/compare/brevo-vs-sendgrid.md)
- [Brevo API + MCP vs SendLayer](https://www.anchorterminal.com/compare/brevo-vs-sendlayer.md)
- [Brevo API + MCP vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/brevo-vs-smtp2go.md)
- [Brevo API + MCP vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/brevo-vs-zoho-zeptomail.md)
- [Cloudflare Email Service vs MailPace](https://www.anchorterminal.com/compare/cloudflare-email-service-vs-mailpace.md)
- [Groundmail API + MCP vs MailPace](https://www.anchorterminal.com/compare/groundmail-vs-mailpace.md)
- [Loops API + MCP vs MailPace](https://www.anchorterminal.com/compare/loops-vs-mailpace.md)
- [MailerSend vs MailPace](https://www.anchorterminal.com/compare/mailersend-vs-mailpace.md)
- [Mailgun API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailgun-vs-mailpace.md)
- [Mailjet API + MCP vs MailPace](https://www.anchorterminal.com/compare/mailjet-vs-mailpace.md)
- [MailPace vs Mailtrap Email API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-mailtrap.md)
- [MailPace vs Mailchimp Transactional (Mandrill)](https://www.anchorterminal.com/compare/mailpace-vs-mandrill.md)
- [MailPace vs Postmark API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-postmark.md)
- [MailPace vs Resend API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-resend.md)
- [MailPace vs Twilio SendGrid](https://www.anchorterminal.com/compare/mailpace-vs-sendgrid.md)
- [MailPace vs SendLayer](https://www.anchorterminal.com/compare/mailpace-vs-sendlayer.md)
- [MailPace vs SMTP2GO API + MCP](https://www.anchorterminal.com/compare/mailpace-vs-smtp2go.md)
- [MailPace vs Zoho CPaaS (formerly ZeptoMail)](https://www.anchorterminal.com/compare/mailpace-vs-zoho-zeptomail.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp