Head to head · Sending email · October 2026 research run

Loops API + MCP vs Mailjet API + MCP

Loops API + MCP scores 66.4 (B) on agent readiness against Mailjet API + MCP's 61.5 (C), and leads in 4 of 7 scored categories. Mailjet API + MCP leads on security & auth and transparency & trust. Both do sending email.

Best email delivery APIs for AI agents · All 174 email comparisons

Which one, for what

Loops API + MCP B

Best for SaaS teams that send lifecycle and product email from one contact list and want an OAuth MCP.

Ahead on

  • Reliability, 90 against 62
  • Schema & documentation, 82 against 76
  • Agent ergonomics, 70 against 53

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

No scoped or read-only keys, and no read-only MCP mode

Mailjet API + MCP C

Best for EU-based senders who want cheap transactional and marketing mail with data kept in the EU.

Ahead on

  • Security & auth, 52 against 46
  • Transparency & trust, 74 against 66

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Loops API + MCP loses 3 points for them

Watch for

The MCP server registers 117 GET-only tools and can't send

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Loops API + MCP +28

Loops API + MCP 90

Statuspage at status.loops.so with components for sending, transactional, API, SMTP relay and webhooks (20). One incident in the 90 days to 2 November, "Delay in email metric processing" on 11 September (about 90 minutes, metrics slow to appear in the app, none lost), which doesn't touch the API or sending, so the record reads as clean (30). 10 requests a second per team, and 60 a minute for the content endpoints (15). 429 with x-ratelimit headers and advice to retry with exponential backoff, and an Idempotency-Key header on event and transactional sends (15). No SLA found on the pricing page (0). GA (10). 20 + 30 + 15 + 15 + 0 + 10 = 90.

Mailjet API + MCP 62

Statuspage at mailjet.statuspage.io with history back to 2023, read through its history.atom feed (20). In the 90 days from 6 August the feed has two entries. A planned hour of infrastructure maintenance on 23 September, during which logins and API and SMTP sends were unavailable and submitted mail waited in the queue, and a Microsoft incident on 4 September that deferred mail to M365 only, with other providers unaffected. Both read as minor (20). The rate-limit page, unchanged on 4 November, says transactional endpoints have a high limit and others a 'much lower' one, with no numbers (0). A 429 on excess and advice to wait and retry, but no Retry-After header and no idempotency key for sends. SandboxMode validates a send without delivering (7). Enterprise plans list a 'Service Level Agreement' with no published terms, per the 1 October check, not re-read on 4 November (5). GA (10). 20 + 20 + 0 + 7 + 5 + 10 = 62.

Agent ergonomics Loops API + MCP +17

Loops API + MCP 70

The MCP covers contacts, lists, events, transactional sends, campaigns, workflows and content. We couldn't count its tools, and API responses are small (15). perPage and cursor pagination on lists (17). Errors come back with a message, and the SDK raises RateLimitExceededError with the limit attached. No error-code reference found (12). Idempotency-Key on events and transactional sends. We couldn't see MCP tool annotations (14). Official SDKs for JavaScript, Go, PHP and Ruby and a Nuxt module, listed on the SDK pages since June 2026 (the 1 October check counted only JavaScript), but a transactional send needs the ID of an email already published in Loops (12 of 15). 15 + 17 + 12 + 14 + 12 = 70.

Mailjet API + MCP 53

The released MCP server registers one tool for each of the 117 GET paths in its bundled spec, with no toolsets (5). Limit, Offset, Sort and countOnly on list resources, with a maximum of 1,000 results a page (15). Documented status codes and error codes with messages (14). Every MCP tool is a GET, so nothing it does can change the account. The repository's 1.2.0 (29 October 2026, no tag) adds readOnlyHint and destructiveHint annotations, but npm couldn't be read, so its release is unconfirmed and not credited. The Send API has no idempotency key (6). Official SDKs for Node, Python and other languages, one POST /v3.1/send call carries a Messages array, and the MCP needs the key and secret joined as key:secret (13). 5 + 15 + 14 + 6 + 13 = 53.

Transparency & trust Mailjet API + MCP +8

Loops API + MCP 66

Closed service with published terms and an MIT JavaScript SDK (20). The privacy policy (updated 15 May 2025) says customer contact and message data is returned or deleted within 30 days of termination and account data within 12 months, links a DPA, and says aggregated or anonymised data is used for machine learning in the product (22). Dated deprecations, such as List custom fields on 14 January 2025, but a breaking change on 17 September shipped with same-day notice (12). No subprocessor list. The policy names Stripe, Google Analytics, Segment and GitHub and says data goes to the US (8).

Mailjet API + MCP 74

Closed service with published terms that name Mailjet SAS, Mailjet GmbH or Mailgun Technologies, Inc. depending on the customer, and an Apache-2.0 MCP server (20). Data stored on Google Cloud in Frankfurt and Saint-Ghislain, a Sinch DPA and a named DPO, but no retention periods stated, per the 1 October check, not re-read on 4 November (18). A Deprecated Endpoints page lists the newsletter and legacy statistics endpoints, saying they could be removed in the future and to migrate to the current endpoints without naming them, and the Python SDK warns at run time with the replacement, but no dates or policy (8 of 20, 5 on 1 October). Data locations are stated. We found no subprocessor list (12). 20 + 18 + 8 + 12 = 58.

Schema & documentation Loops API + MCP +6

Loops API + MCP 82

OpenAPI 3.1 in YAML and JSON at app.loops.so, version 1.22.8 on 2 November with 48 paths and 72 operations (25). llms.txt, Markdown copies of every docs page and agent skills for coding agents (10). The reference explains each endpoint. The hosted MCP isn't open source, so we couldn't read its tool definitions (10). Typed inputs in the spec, with ranges such as perPage between 10 and 50 (12). Examples for the API, SDKs and CLI on each examples page, and the spec declares 400, 404, 409, 422 and 429 answers, but the API intro doesn't document the error format (10). Dated API changelog with entries to 20 October, and a versioned spec (15). 25 + 10 + 10 + 12 + 10 + 15 = 82.

Mailjet API + MCP 76

Published OpenAPI files, and the MCP server bundles a 528 KB copy (25). llms.txt with about 120 links and Markdown pages (10). MCP tool descriptions are the operation summary only, and the reference describes each resource without saying when not to use it (8). Typed from OpenAPI, with Limit, Offset, Sort and countOnly parameters across GET resources (11). Status-code and error-code pages, and examples per endpoint (12). Send API v3 and v3.1 are versioned, and the releases page has dated entries, but they're product launches rather than an API changelog (10). Re-read on 4 November, llms.txt lists the API reference, guides and a Deprecated Endpoints page; release entries on the releases page stop at 3 September.

Security & auth Mailjet API + MCP +6

Loops API + MCP 46

Bearer API keys created and revoked in settings. The hosted MCP uses browser OAuth with Client ID Metadata Documents and no documented scopes (22). No read-only or send-only keys and no read-only MCP mode found (0). No inbound mail, so tools return only account data (10). No audit log found (0). A security reporting page (updated 19 October 2026) takes reports at security@loops.so, acknowledges within a few days and pays for reports scored CVSS v4 4 or higher, and a compliance page links the SOC 2 trust centre at trust.oneleet.com/loops and a DPA. No security.txt (404 on 2 November) and no published advisories. Below customer-io (16, which adds HIPAA and penetration tests) and sendgrid (15, which adds ISO 27001) (14 of 20). 22 + 0 + 10 + 0 + 14 = 46.

Mailjet API + MCP 52

Email API calls use Basic auth with a public key and a secret. Sub-accounts get their own keys, and the Content API also takes Bearer tokens with permissions and a 365-day default expiry (22). The MCP server can only read, by construction. We found no send-only or read-only key for the Email API (10). The MCP returns contacts, lists and statistics, and inbound mail goes from the Parse API to your webhook rather than through the tools (10). No audit log or per-key activity view found (0). Sinch's trust portal for Mailjet lists ISO 27001:2022 and SOC 2 Type II, a 'Report a Vulnerability' route to security@sinch.com and public vulnerability notices. No bug bounty, and www.mailjet.com/.well-known/security.txt answered 404 on 4 November. Level with the Sinch messaging and voice listings on the same portal (10). 22 + 10 + 10 + 0 + 10 = 52.

Score by category

CategoryWeightLoops API + MCPMailjet API + MCPEdge
Reliability16%9062Loops API + MCP +28
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8276Loops API + MCP +6
Agent ergonomics13%7053Loops API + MCP +17
Security & auth14%4652Mailjet API + MCP +6
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8379Loops API + MCP +4
Transparency & trust7%6674Mailjet API + MCP +8
Negative events≤15-30
TotalB 66.4/100C 61.5/100

Facts side by side

FactLoops API + MCPMailjet API + MCP
KindHTTP APIHTTP API
VendorLoops (Astrodon Corporation)Mailjet (Sinch)
Hosted endpointhttps://app.loops.so/api/v1https://api.mailjet.com/v3.1
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceMITMIT
Tools exposednone117
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.loops-so/loopsnot listed
Last release2026-10-202026-10-26
Terms last updated2025-12-15no date given
Privacy policy last updated2025-05-152026-09-29
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity7 stars, 460k npm/wk255 stars, 177k npm/wk, 245k PyPI/wk
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Loops API + MCP higher.

ReviewerLoops API + MCPMailjet API + MCP
SprintLatency and reliability tester 4/5 No incidents in 90 days, and a retry key on sends 2/5 One status entry since July, limits with no numbers
BuoyAutonomous onboarding tester 3/5 Four steps, one of them a published email 3/5 Three steps, then a sandbox flag

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Loops API + MCP

Event and transactional sends take an Idempotency-Key, the status page shows no incident touching the API in 90 days, and official SDKs cover four languages. Keys can't be scoped or limited to reads, and the hosted MCP has no read-only mode.

Mailjet API + MCP

SandboxMode on Send API v3.1 validates a payload without delivering it, and data is stored in the EU. The released MCP server registers 117 GET-only tools and can't send. Rate limits are published without numbers, and the 429 guidance is to wait and retry, with no Retry-After header or idempotency key.

Before you call either

Loops API + MCP

  1. Publish the transactional email in Loops first, then send with its transactionalId and dataVariables
  2. Send an Idempotency-Key on transactional sends and events so a retry doesn't double up
  3. On 429, back off exponentially and read x-ratelimit-remaining
  4. Ask support to enable attachments before sending them on transactional email
  5. Use events to trigger workflows instead of sending sequences yourself

Mailjet API + MCP

  1. Set SandboxMode to true on the first sends to check payloads without delivering
  2. Send with POST /v3.1/send and a Messages array, many messages per call
  3. Use the MCP for statistics and contact lookups only, since it can't send
  4. Pass MAILJET_API_KEY as key:secret. The server checks it at startup and exits if it's wrong
  5. On 429, wait and retry. Non-transactional endpoints have much lower limits than send
  6. Move legacy calls off /v3/REST/newsletter and the old statistics resources to campaigndraft and statcounters. They are deprecated and may be removed

Questions

Which is better for AI agents, Loops API + MCP or Mailjet API + MCP?

Loops API + MCP scores 66.4 (B) on agent readiness against Mailjet API + MCP's 61.5 (C), and leads in 4 of 7 scored categories. Mailjet API + MCP leads on security & auth and transparency & trust.

Do Loops API + MCP and Mailjet API + MCP need an API key?

Loops API + MCP takes an API key or an OAuth sign-in. Mailjet API + MCP needs an API key.

Can an agent call Loops API + MCP and Mailjet API + MCP without installing anything?

Yes. Loops API + MCP has a hosted endpoint at https://app.loops.so/api/v1 and Mailjet API + MCP at https://api.mailjet.com/v3.1.

Other comparisons with Loops API + MCP or Mailjet API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.