Mailjet sends marketing and transactional mail with an inbound parse route. MCPmailer stores and threads the conversation an agent holds.
Transactional email APIs · Mailjet claims checked July 2026
Mailjet, part of the same group as Mailgun, is a straightforward sender with marketing and transactional in one product, collaborative template editing, and a parse route for inbound mail. Paid plans start around seventeen dollars a month for fifteen thousand emails.
If non-technical colleagues need to edit templates while developers use the API, Mailjet's collaborative editor is a real advantage and its pricing at moderate volume is competitive.
Templates and volume are not the problem an agent has. It needs the message it just received to belong to a conversation it can read back, a way to wait for an answer, and limits that understand the difference between replying and cold outreach.
A parse route delivers a decoded message to your endpoint. Everything after that, thread linkage, storage, retention, a search index, is yours. Ours are part of the mailbox and reachable as tools.
Collaborative template editing is a genuinely good feature for a marketing team and irrelevant to a model writing prose. Message bodies here are markdown, delivered as text plus HTML, because that is what a model produces well.
A sender key on a domain can send as anything on that domain. A key here is scoped to one mailbox and cannot see the other identities, notes, or secrets in the workspace unless granted.
Every row is a claim we could defend with their documentation open beside it. Where they are ahead, the row says so.
Same pattern as any transactional sender: keep it, and move the conversations.
Product and campaign mail stays
Templates and lists keep their home.
Agent addresses come here
On a subdomain, with per-agent keys.
Delete the parse route
For those addresses only, along with the handler behind it.
For sending, yes. For an inbox, you would build the mailbox, threading, storage, and search on top of a parse route.
Mailjet publishes around seventeen dollars a month for fifteen thousand emails. Our Pro plan is twenty for ten thousand and includes receiving, threading, search, and a dashboard, so compare the whole job rather than the send.
For your product mail, yes. Agent messages are markdown, which is what a model writes well.
No. There is no surface here for a marketing team, deliberately.
A parse route can deliver inbound mail to your endpoint, which covers receiving. What is missing is the mailbox it belongs to: unread state, a thread to continue, retained bodies, and a search index the agent can query before it answers.
Ours, for this job. Mailjet's free allowance is aimed at sending; ours includes receiving, threading, search, and three agent inboxes at 3,000 emails a month with no card.
Keep your transactional sender for the mail your product sends. This is for the addresses your agents converse from, which is a different job with different failure modes.
The free tier is 3,000 emails a month across three agent inboxes, no card, with receiving, threading, and search included. Enough to watch a real conversation happen before you decide.
More Transactional email APIs