A Mailjet MCP that covers the whole account, not just the send call
Connect one Mailjet API key and secret key pair and 71 nodes land on the canvas: contacts, lists and custom properties, bulk writes and CSV import, segments, campaign drafts through content, test, schedule and send, sent campaigns and messages, statistics and the raw open, click and bounce logs, templates, senders and domain verification, Event API webhooks and inbound parse routes. An AI agent can look up how a campaign performed, add a contact to the right list, and open a task when a domain check fails, without anyone signing in to Mailjet.
What the Mailjet MCP connector does
The Mailjet connector for Mattering Automations is 71 nodes: 35 read nodes and 36 action nodes, built from Mailjet's own published API guides rather than from a summary of them. It reaches contacts and contact lists, custom contact properties, segments, the bulk contact writers and the two step CSV import, marketing campaign drafts through their whole life cycle, the sent campaigns and per message records behind them, statistics and the raw event logs underneath the statistics, templates and template bodies, senders and sender domain verification, Event API webhooks, and inbound parse routes. One credential authenticates all of it. Mailjet is part of Sinch.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP capable assistant can use them, alongside Matter, the AI assistant built into the platform. An agent can read a campaign's numbers with Mailjet: Get Stat Counters, find out which mailbox providers are struggling with Mailjet: Get Recipient ESP Statistics, subscribe a new signup with Mailjet: Add Contact To List, and leave the sending nodes alone entirely, because sending is gated separately.
One thing about Mailjet shapes the whole connector, and it is better said out loud than discovered in production. Mailjet is not one versioned API on one base URL: several generations are current at the same time and each endpoint belongs to exactly one of them. Contacts, lists, campaigns, statistics, templates, senders, webhooks and parse routes are on the v3 REST surface. The CSV upload is on a separate v3 data plane that takes a raw text body. Sending is on v3.1. Contact deletion, which is a GDPR anonymization rather than a row removal, is the one v4 endpoint. The connector carries the version in each node so you never have to think about which one you are on, but it explains why the node catalog looks broader than a single reference page suggests.
The safety modeling is stated rather than implied. 15 of the 71 nodes are flagged destructive, and five of those send mail: Mailjet: Send Message, Mailjet: Send Campaign Email, Mailjet: Send Campaign Draft, Mailjet: Schedule Campaign Draft and Mailjet: Test Campaign Draft. The one Mailjet calls a test still puts real mail in real inboxes, and the scheduled send reaches real people with no second approval, which is why it carries the same flag as an immediate one. Three more write contacts at scale with actions that can suppress addresses account wide: Mailjet: Manage Many Contacts, Mailjet: Manage List Many Contacts and Mailjet: Create CSV Import. The remaining seven delete, and Mailjet: Delete Contact is the sharpest of them, because the GDPR deletion anonymizes the address rather than removing the record: it cannot be recovered, and re adding the address creates a fresh contact with no history.
One connection, three surfaces
- Visual automations. Drag Mailjet nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Mailjet node, ready to drop on the canvas
71 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 35
Mailjet: Get Anonymized Contact
Read back a contact after a GDPR deletion to confirm the anonymization landed: the address becomes a hashed @domain.invalid value and the name becomes Anonymized. Same endpoint as Mailjet: Get Contact, kept separate because it is the documented verification step of the deletion flow and takes the numeric id only.
Mailjet: Get CSV Import
Poll a CSV import job: Status moves through Upload and Parse to Completed, Count is the rows processed and Errcount the rows that failed. A non-zero Errcount means part of the file did not land.
Mailjet: Get Campaign
Fetch one campaign by id, or by the mj.nl=<draft id> form that resolves a campaign draft to the campaign it produced. That second form is how a workflow that created and sent a draft finds the campaign id its statistics live under.
Mailjet: Get Campaign Draft
Fetch one campaign draft, including its Status: the field that says whether it is still editable, programmed for a future send, or already delivered. Check this before any send or schedule call.
Mailjet: Get Campaign Draft Content
Read the HTML and plain-text bodies stored on a campaign draft, plus its MJML source when the draft was built that way. Note the property names carry hyphens: Html-part and Text-part.
Mailjet: Get Contact
Fetch one contact by numeric id or by email address. This is how you turn an address into the contact id every other contact node wants. The row still arrives inside the standard envelope, so read it at data.Data[0].
Mailjet: Get Contact List
Fetch one contact list: name, subscriber count, creation date, and the magic-list Address that lets Send API mail the whole list by writing to <address>@lists.mailjet.com.
Mailjet: Get Contact Lists
List the contact lists one contact belongs to, with the subscription date and whether the contact has unsubscribed from each. IsUnsub true means they are still on the list but opted out, which is not the same as not being a member.
Mailjet: Get Domain
Fetch one sender domain by id or by domain name: the exact DKIM record name and value, the SPF value, the ownership token, and when each was last checked.
Mailjet: Get Geo Statistics
Opens and clicks grouped by the recipient's country, optionally narrowed to one campaign. Lifetime figures, not a time series.
Mailjet: Get Link Click Statistics
Total and unique clicks for each URL in one campaign's email, with the link's position in the body. These are lifetime figures for the campaign, not a time series: re-fetch rather than trying to add them across periods.
Mailjet: Get List Many Contacts Job
Poll an asynchronous list subscription job until its Status is Completed. Needs both the list id the job was started on and the JobID it returned.
Mailjet: Get Many Contacts Job
Poll an asynchronous bulk contact job until its Status is Completed, and read how many rows it processed. A non-empty ErrorFile means some rows failed and names where the detail is.
Mailjet: Get Message
Fetch one sent message by id: its current status (queued, sent, opened, clicked, bounced, spam), arrival time, attempt count and the campaign and contact it belongs to.
Mailjet: Get Message History
List every event recorded against one message in order: sent, opened, clicked, bounced, unsub, with the Unix timestamp of each. This is the per-message audit trail behind the aggregate statistics.
Mailjet: Get Recipient ESP Statistics
Delivery and engagement for one campaign broken down by the recipient's mailbox provider, which is how you tell a provider-specific deliverability problem from a content one. The row carries real RATE columns (OpenRate, ClickThroughRate, the bounce and spam rates) alongside the counts: rates are per-provider ratios and must never be added together.
Mailjet: Get Stat Counters
The account's main statistics endpoint: delivery and engagement counters for one campaign, one list, or the whole API key, either as a lifetime total or as a time series. CounterTiming decides what a bucket MEANS, and the choice matters: Event buckets by when the open or click happened and stops changing once the day is past, while Message buckets by send time and keeps being revised as engagement arrives days later. Mailjet documents two response shapes for this one endpoint, so read rows from data.Data or, on sub-lifetime resolutions, from data.StatCounters.Data.
Mailjet: Get Template
Fetch one template's metadata: name, description, author, editor mode and intended purpose. The body itself lives on a separate resource, Mailjet: Get Template Content.
Mailjet: Get Template Content
Read a template's stored HTML and plain-text bodies, its MJML source, and its Headers object of default From, Subject and Reply-To values. Note the hyphenated property names: Html-part and Text-part.
Mailjet: List Bounce Events
The raw bounce log: one row per bounce with its timestamp, campaign and contact, whether the address was blocked, and whether the failure is permanent. Permanent bounces are the addresses to stop mailing; retrying them is how a sending reputation gets damaged.
Mailjet: List Campaign Drafts
List the marketing campaign drafts on the account with their titles, subjects, sender, audience list and status. The draft id from here feeds the content, test, send and schedule nodes.
Mailjet: List Campaigns
List the campaigns that have actually been sent, marketing and transactional alike. A campaign here is the delivery record, distinct from the campaign DRAFT that produced it; the campaign id is what the statistics nodes take.
Mailjet: List Click Events
The raw click-event log: one row per click with the URL, the timestamp, the delay between send and click, and the campaign and contact. Defaults to today; widen it with FromTS and ToTS.
Mailjet: List Contact Lists
List the contact lists on the account with their ids, names, subscriber counts and magic-list addresses. The list id from here feeds every list-scoped node and every campaign recipient field.
Mailjet: List Contact Properties
List the custom contact properties defined on the account with their datatypes. These are the names usable in contact Properties objects, in segment expressions, and in campaign personalization.
Mailjet: List Contact Statistics
Per-contact lifetime engagement: how many messages each contact was delivered, opened, clicked, bounced or complained about, and when they were last active. Useful for building an engaged-recipients segment or pruning dead addresses.
Mailjet: List Contacts
List the contacts on the account with their ids, addresses, delivery counts and exclusion state. Pages of 10 by default and a maximum of 1000, so a large account is read by walking Offset. Rows come back under data.Data.
Mailjet: List Domains
List the sender domains on the account with their SPF and DKIM records and current verification status. The record values here are what has to be published in DNS before Mailjet will treat the domain as authenticated.
Mailjet: List Event Callbacks
List the Event API webhooks configured on the account: which URL receives which event type, at which payload version. Version 2 is the grouped format that batches several events into one POST.
Mailjet: List Messages
List sent messages with their delivery status, campaign and contact. Filter by the CustomID a send attached, or by ContactAlt to find every message sent to one address. This is how a transactional workflow answers did that email arrive without standing up a webhook.
Mailjet: List Open Events
The raw open-event log: one row per open with its timestamp, campaign, contact and user agent. Defaults to today; pass FromTS and ToTS to widen the window. This is the pull equivalent of the open webhook, for workflows that cannot host a receiver.
Mailjet: List Parse Routes
List the inbound Parse API routes on the account: each maps an address to a webhook URL that receives the parsed email as JSON. This is the mechanism behind reply capture.
Mailjet: List Segments
List the segments (contact filters) on the account with the expression each one evaluates. A segment id narrows a campaign draft's audience without creating a second list. Status used means at least one campaign references it.
Mailjet: List Senders
List the email addresses and domains registered as senders on this API key, with their validation status. Only an Active sender may be used in a send, so this is both the credential health check to run first in any Mailjet automation and the source of every sender picker. Rows come back under data.Data.
Mailjet: List Templates
List email templates. OwnerType user returns the account's own templates, which are the editable ones; the default includes Mailjet's shared gallery. The template id feeds both the Send API TemplateID property and campaign drafts.
Action nodes 36
Mailjet: Add Contact To List
Create a contact and subscribe it to one list in a single call, setting its custom properties at the same time. This is the everyday signup path. Action addforce also clears a previous unsubscribe; addnoforce respects it; remove and unsub take the contact off or opt it out. Property names must already exist on the account.
Mailjet: Check Domain
Run Mailjet's SPF and DKIM verification against a sender domain right now instead of waiting for the periodic check. Returns the values currently published in DNS alongside any errors, so a failing domain says what is actually there rather than only that it is wrong. Changes no configuration.
Mailjet: Create CSV Import
DESTRUCTIVE: start the bulk import of a staged CSV. It writes contacts and property values at file scale with no undo, and the Method decides how brutal it is: addforce clears existing unsubscribes, remove and unsub strip or opt out everyone in the file, and excludemarketing suppresses every listed address from ALL marketing on the account. Returns a job row; poll it with Mailjet: Get CSV Import.
Mailjet: Create Campaign Draft
Create a marketing campaign draft: who it comes from, what the subject line is, and which list (optionally narrowed by a segment) it will reach. This creates the shell only and sends nothing. Add a body with Mailjet: Set Campaign Draft Content, then send or schedule it.
Mailjet: Create Contact
Create a contact from an email address. This creates the contact on the ACCOUNT only; it does not subscribe it to anything. Use Mailjet: Manage Contact Lists or Mailjet: Add Contact To List afterwards. Reversible with Mailjet: Delete Contact.
Mailjet: Create Contact List
Create a contact list. Only a name is required; Mailjet assigns the id and the magic-list address. Reversible with Mailjet: Delete Contact List.
Mailjet: Create Contact Property
Define a new custom contact property. It has to exist before any contact can carry a value for it, so this is the first step of any personalization or segmentation work. Reversible with Mailjet: Delete Contact Property.
Mailjet: Create Event Callback
Point an Event API webhook at your endpoint so Mailjet POSTs delivery and engagement events as they happen. One callback per event type, or use the all event type to receive every kind. Version 2 groups several events into one POST, which is what a high-volume receiver wants. Reversible with Mailjet: Delete Event Callback.
Mailjet: Create Parse Route
Create an inbound parse route. Supply only the URL and Mailjet generates an address on parse-in1.mailjet.com to forward mail to; supply an address on a domain you have already pointed at Mailjet with an MX record to use your own. Mail arriving at that address is POSTed to the URL as JSON with headers, parts and attachments. Point a campaign's Reply-To at it to capture replies.
Mailjet: Create Segment
Create a segment from a filter expression over contact properties, for example age>40 or country="US" AND age>30. Expressions combine property comparisons with AND, OR and NOT; every property named must already be defined. The segment is then attached to a campaign draft through its SegmentationID.
Mailjet: Create Sender
Register an email address, or a whole domain with the *@ form, as a sender on this API key. The new sender starts Inactive: Mailjet emails a confirmation link, or you can prove ownership with a DNS TXT record or a file at the domain root and then call Mailjet: Validate Sender. Nothing can be sent from it until it is Active.
Mailjet: Create Template
Create a template. This creates the metadata shell only and the template has no body until Mailjet: Set Template Content runs against the returned id. Reversible with Mailjet: Delete Template.
Mailjet: Delete Contact
DESTRUCTIVE and irreversible: the GDPR contact deletion. Mailjet anonymizes the contact rather than removing the row, replacing the address with a hashed @domain.invalid value and the name with Anonymized, and strips its personal data everywhere on the account. The original address cannot be recovered, and re-adding it creates a NEW contact with no history. This node is the one call in the connector that goes to the v4 API, and it takes the numeric contact id only, never an email.
Mailjet: Delete Contact List
DESTRUCTIVE: delete a contact list. The contacts themselves survive on the account, but the list, its membership and its campaign associations are gone, and any campaign draft pointing at it loses its audience. There is no undo from here; the reversible alternative is Mailjet: Update Contact List with IsDeleted true, which soft-deletes instead.
Mailjet: Delete Contact Property
DESTRUCTIVE: delete a custom contact property definition. Every contact's stored value for it goes with it, and any segment expression or campaign personalization referencing the name stops resolving. Recreating the property does not bring the values back.
Mailjet: Delete Event Callback
DESTRUCTIVE: remove an Event API webhook. Mailjet stops delivering that event type immediately and does NOT replay the events that occur while no callback exists, so whatever happens in the gap is lost rather than delayed.
Mailjet: Delete Parse Route
DESTRUCTIVE: delete an inbound parse route. Mail sent to that address stops being forwarded to your webhook, and a Mailjet-generated address is not reissued, so any campaign whose Reply-To points at it silently loses its replies.
Mailjet: Delete Segment
DESTRUCTIVE: delete a segment. The expression is gone and any campaign draft pointing at it loses its audience narrowing, which means the next send reaches the WHOLE list rather than failing. The reversible alternative is Mailjet: Update Segment with Status deleted.
Mailjet: Delete Template
DESTRUCTIVE: delete a template and its stored body. Any send or campaign draft still referencing the id starts failing with error send-0010, and the content cannot be recovered.
Mailjet: Manage Contact Lists
Subscribe or unsubscribe ONE contact across several lists in a single call. Each entry names a list id and an action: addforce adds and clears any previous unsubscribe, addnoforce adds but leaves an existing unsubscribe standing, remove takes the contact off the list, and unsub marks it unsubscribed while keeping the membership row.
Mailjet: Manage List Many Contacts
DESTRUCTIVE: apply one subscription action to many contacts on one list at once, creating any that do not exist. It OVERWRITES the properties it is given at whatever scale the payload has with no undo, and Action remove or unsub strips or opts out every contact in the payload in one shot. Runs asynchronously and returns a JobID; poll it with Mailjet: Get List Many Contacts Job.
Mailjet: Manage Many Contacts
DESTRUCTIVE: create or update many contacts at once and, optionally, apply list actions to all of them. It OVERWRITES the properties it is given on contacts that already exist, at whatever scale the payload has, with no undo, and setting IsExcludedFromCampaigns true here suppresses every listed contact from all marketing on the account. Runs asynchronously and returns a JobID; poll it with Mailjet: Get Many Contacts Job.
Mailjet: Schedule Campaign Draft
DESTRUCTIVE: schedule the campaign to go out at a future date. Flagged the same as an immediate send because it reaches real people with no second approval, and this connector ships no unschedule node, so from here it is a one-way door: cancelling means going into the Mailjet interface. The draft's Status becomes programmed.
Mailjet: Send Campaign Draft
DESTRUCTIVE and irreversible: send the campaign to its entire audience list right now. Every contact on the list, minus any segment narrowing and the exclusion list, receives real email within minutes and there is no recall. Confirm the audience and the body before wiring this into anything automatic.
Mailjet: Send Campaign Email
DESTRUCTIVE: send one campaign email through Mailjet. Real mail to a real inbox, no recall. Uniform ESP contract: the same params and the same result envelope as the Postmark, Mailgun and SMTP campaign-send nodes, so a caller does not branch on provider. Returns {ok, provider, provider_message_id} or {ok: false, error, detail, retryable}, with a send failure arriving as HTTP 200 and ok false rather than as a transport error. Exactly one recipient per call; from_email must be a validated Mailjet sender or the send is refused with send-0008. headers are passed through verbatim, which is how compliance headers such as List-Unsubscribe arrive, and metadata is carried as the message's EventPayload.
Mailjet: Send Message
DESTRUCTIVE: send transactional email through Send API v3.1. It delivers real mail to real inboxes and there is no recall, which is why it is flagged destructive even though it deletes nothing. Set SandboxMode true to have Mailjet validate the payload and return the normal response without delivering anything. Up to 50 recipients across To, Cc and Bcc per message, and several messages per call. Read results at data.Messages[]: a call can return HTTP 200 with some messages succeeded and others carrying Status error, so check per message rather than trusting the status code. For campaign sending with a uniform cross-provider contract, use Mailjet: Send Campaign Email instead.
Mailjet: Set Campaign Draft Content
Set the body of a campaign draft. Supply HTML, plain text, or both. Updating the MJML source does NOT regenerate the HTML automatically, so a draft edited that way needs its HTML written too or it goes out with the old body.
Mailjet: Set Template Content
Set a template's body, and optionally its default From, Subject and Reply-To through the Headers object, so a send using the template does not have to repeat them. Anything the send supplies overrides these defaults. Storing MJML does not regenerate the HTML, so write html_part too.
Mailjet: Test Campaign Draft
DESTRUCTIVE: send a preview of the campaign to the named test recipients. It is called a test, but it puts real email in real inboxes and cannot be recalled, so it is flagged the same as any other send. The campaign itself stays a draft.
Mailjet: Update Campaign Draft
Change a campaign draft's subject, sender, audience list or segment. Blank fields are left alone, since Mailjet treats every PUT as a partial update. Only drafts that have not been sent can be changed.
Mailjet: Update Contact
Update a contact's name or exclusion state. Mailjet treats every PUT as a partial update, so fields you leave blank keep their current values rather than being cleared. Setting IsExcludedFromCampaigns true is the documented way to add someone to the exclusion list; it suppresses them from ALL marketing on the account, not just one list.
Mailjet: Update Contact Data
Set the custom property values on one contact: the fields campaign personalization reads. Every property named here must already be defined on the account with Mailjet: Create Contact Property, otherwise the call is refused with Property not defined.
Mailjet: Update Contact List
Rename a list, or flip its deleted flag. Mailjet treats every PUT as a partial update, so blank fields are left alone. Setting IsDeleted false is how a soft-deleted list is brought back.
Mailjet: Update Segment
Change a segment's name, expression or description. Blank fields are left alone, since Mailjet treats every PUT as a partial update. Editing the expression changes who a campaign using this segment will reach, so check which drafts reference it first.
Mailjet: Upload CSV Data
Upload CSV contact data against a list and get back a data id. This stages the file only; nothing is imported until Mailjet: Create CSV Import runs against the returned id. The first CSV row is the header and must contain an email column; other columns must match existing contact property names. Read the id at data.ID, which is NOT the usual envelope.
Mailjet: Validate Sender
Ask Mailjet to re-check a pending sender's ownership proof (the TXT record or the file at the domain root) and activate it if the proof is in place. Returns the per-method errors when it is not, which is what tells you whether the DNS record or the file is the missing half.
Connecting Mailjet takes one credential
Mailjet authenticates every request with a two part key pair over HTTP Basic: the API Key is the username and the Secret Key is the password. This is not a single bearer token, and a connector that asked for one field could not authenticate at all. Both halves are generated with the account and are shown together in the Mailjet app under Account settings, then API Key Management. There is one global host, so nothing about the URL depends on your account: no region field, no environment field, no account subdomain. Worth knowing before you plan a workflow around volume: Mailjet publishes no general request rate limit for its REST API in its guides, and documents no 429 shape for it, so this page quotes no requests per second figure. What Mailjet does document is per request size: attachments that its guide says should not exceed 15 MB, and a pagination Limit that defaults to 10 and tops out at 1000. Check Mailjet's own pricing page for what your plan includes, including whether API access is part of it, before you build a workflow that assumes it.
Sign in to Mailjet, open Account settings, then API Key Management, and copy both halves of the pair: the API Key and the Secret Key.
In Mattering Automations, open Connectors, click Add Connector, choose Mailjet, and create a credential with the API Key in the first field and the Secret Key in the second.
Click Test Connection. Mattering calls Mailjet's sender list endpoint, which needs no parameters and one global host: a list, even a short one, proves the pair, and a 401 means one of the two halves is wrong.
All 71 Mailjet nodes appear in the canvas palette. Run Mailjet: List Senders first. Only a sender whose status is Active can be used in a send, so this is both the connection proof and the list of addresses any sending workflow is allowed to use.
Common uses for the Mailjet MCP
Turn a signup anywhere into a subscribed contact
Mailjet: Add Contact To List creates the contact and subscribes it to one list in a single call, custom properties included, which is the everyday path from a form, a CRM record or an agent's decision to a real subscriber. Mailjet: Manage Contact Lists handles the multi list case for one contact, adding to some lists and unsubscribing from others in one request. Mailjet: Update Contact Data sets the property values that campaign personalization reads later. Because these are nodes rather than a script, the same workflow can write the person into a Mattering database, open a task for an owner, and notify a channel in the same run.
Report on a campaign without opening the dashboard
Mailjet: Get Stat Counters is the account's main statistics read: delivery and engagement counters for one campaign, one list, or the whole API key, either as a lifetime total or as a time series. Mailjet: Get Link Click Statistics breaks a campaign down by the URLs inside the email, Mailjet: Get Recipient ESP Statistics breaks it down by the recipient's mailbox provider, which is how you tell a provider specific deliverability problem from a content problem, and Mailjet: Get Geo Statistics groups opens and clicks by country. A scheduled workflow can write all of it into a Mattering database and open a task only when a number moves further than it should have.
Watch deliverability instead of hearing about it later
Mailjet: List Bounce Events is the raw bounce log, one row per bounce with its campaign, its contact, whether the address was blocked and whether the failure is permanent. Mailjet: List Domains and Mailjet: Get Domain return the exact DKIM and SPF records for a sender domain with the last check time, and Mailjet: Check Domain runs Mailjet's verification against DNS right now instead of waiting for the periodic check. That is a workable weekly sweep: check every sending domain, read the bounce log for permanent failures, and open one task with both findings when either one moves.
Build a campaign draft in a workflow and stop before the send
Mailjet: Create Campaign Draft creates the shell, Mailjet: Set Campaign Draft Content puts the HTML and plain text bodies on it, and Mailjet: Get Campaign Draft reads back the status that says whether the draft is still editable, programmed for a future send, or already delivered. Assembling a campaign is safe work that an automation or an agent can do end to end. The last step is the one to keep human: Mailjet: Send Campaign Draft mails the entire audience list and cannot be recalled, and Mailjet: Schedule Campaign Draft is flagged identically because it reaches real people with no second approval and this connector ships no node to unschedule it. Put an approval task between the draft and the send.
Import a list properly, in the two steps Mailjet actually uses
Bulk contact loading is a real trap for a first time builder, because it is not one call. Mailjet: Upload CSV Data stages the file against a list and returns a data id, and nothing is imported until Mailjet: Create CSV Import runs against that id. Mailjet: Get CSV Import then polls the job: Status moves through Upload and Parse to Completed, Count is the rows processed, and a non zero Errcount means part of the file did not land. Mailjet: Manage Many Contacts and Mailjet: Manage List Many Contacts are the JSON equivalents for smaller batches, with Mailjet: Get Many Contacts Job and Mailjet: Get List Many Contacts Job as their pollers. All three writers are flagged destructive, because they overwrite properties at file scale and their actions include ones that suppress addresses account wide.
Keep the sender list and the template library honest
Mailjet: List Senders shows every address and domain registered on the key with its validation status, and Mailjet: Create Sender, Mailjet: Validate Sender and Mailjet: Check Domain cover the rest of that life cycle. Mailjet: List Templates, Mailjet: Get Template Content and Mailjet: Set Template Content do the same for the bodies your sends reference. Two facts worth building around, both from Mailjet's own guides: only an Active sender can send, and updating a template's MJML source does not regenerate its HTML, so a template edited that way goes out with the old body unless the HTML is written too.
Example: A weekly deliverability sweep that files its own follow up
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a weekly schedule fires.
Mailjet: List Senders and Mailjet: List Domains read the current sending estate. Raise the Limit on both: Mailjet's pagination Limit defaults to 10, so an unraised limit quietly truncates the list on any real account.
Mailjet: Check Domain runs verification against each sending domain now, and returns what is actually published in DNS next to what Mailjet expects.
Mailjet: Get Stat Counters pulls the week's delivery and engagement counters, with the counter resolution set to Day so the response is a time series rather than one undated row.
Mailjet: List Bounce Events reads the raw bounce log for the same window, with the timestamps widened past the default of today, and a condition looks at how many of them are permanent.
The numbers land in a Mattering database next to last week's, and a task opens for a person only when a domain check fails or permanent bounces move outside their usual band. Nothing in this workflow sends mail, so it can run unattended.
Mailjet MCP questions, answered
What Mailjet operations are supported?
71 nodes: 35 read nodes and 36 action nodes. Contacts, including creation, update, list membership, custom property values, per contact statistics and the GDPR deletion with its anonymized read back. Contact lists, custom contact properties and segments. The bulk writers and the two step CSV import with their polling nodes. Marketing campaign drafts through create, content, test, schedule and send, plus the sent campaigns and the per message records and message history behind them. Statistics, and the raw open, click and bounce logs underneath them. Templates and template bodies. Senders and sender domain verification. Event API webhooks and inbound parse routes. Deliberately not included: Mailjet's sub account API key endpoints, because their documented response body echoes live key material into run output and logs, and Mailjet's SMS product, which is a separate API with its own token.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Does Mailjet publish its own MCP server?
Not that we could find. Mailjet's published API documentation, its guides and its list of official client libraries mention no MCP server: it ships REST wrappers for PHP, Python, Node.js, Java, .NET, Go and Ruby, and nothing MCP shaped. So if you searched for a Mailjet MCP and found nothing official, that matches what we found. This connector is the answer to that search: 71 nodes over MCP, usable by Claude, ChatGPT or Matter, and usable as ordinary steps on an automation canvas on a schedule with nobody present. If Mailjet ships its own server later, we will say so here and say plainly what it does better.
Why does the credential ask for two fields instead of one API key?
Because Mailjet's API is HTTP Basic with a two part key pair rather than a single bearer token: the API Key is the username and the Secret Key is the password. Both halves are generated with your account and shown together in Mailjet's API Key Management screen. A connector that asked for one field would fail to authenticate on every call, so the credential form asks for both and labels them the way Mailjet does.
Can an AI agent send email to my whole list by accident?
The five sending nodes are flagged destructive so you can gate them: Mailjet: Send Message, Mailjet: Send Campaign Email, Mailjet: Send Campaign Draft, Mailjet: Schedule Campaign Draft and Mailjet: Test Campaign Draft. Mail that has gone out cannot be recalled, so the guardrails have to be structural rather than hopeful. Keep agents on the read nodes and the contact nodes, put every send behind a condition or an approval task, and note two specifics. Mailjet: Test Campaign Draft is called a test by the API and still puts real mail in real inboxes. Mailjet: Schedule Campaign Draft is a one way door from the canvas, because this connector ships no node to unschedule a campaign.
How do I know a send actually worked?
By reading the response body, not the status code, and this is the single thing most likely to cost a first time builder an afternoon. A Mailjet send failure arrives as an HTTP 200: the message that failed validation comes back inside a 2xx response with a status of error and an errors array, and one bulk call can carry successes and failures together. A workflow that treats 2xx as proof of delivery will report mail as sent that Mailjet never accepted. Mailjet: Send Campaign Email classifies per message rather than per status code for exactly this reason, and both send nodes say so in their descriptions.
What are Mailjet's rate limits?
Mailjet publishes no general request rate limit for its REST API in its guides, and documents no 429 response shape for it, so we will not quote a number we cannot cite. What Mailjet does document is per request size: attachments that its guide says should not exceed 15 MB, and a pagination Limit that defaults to 10 and tops out at 1000. In practice the constraint that bites first on a sending workflow is your account's sending quota rather than any request rate. Treat unbounded polling as unsafe on principle.
Why is a 403 not an authentication problem?
Because on Mailjet's Send API most 403s are a sender configuration fault rather than a credential fault. The send-0006, send-0007 and send-0008 codes mean the From address is not permitted, not validated, or not authorized on this key, and retrying reproduces them forever. The fix is to register and validate the address with Mailjet: Create Sender and Mailjet: Validate Sender, or to pick an address that Mailjet: List Senders already shows as Active. A genuine authentication failure looks different: mj-0001 means the key is suspended and mj-0015 means no valid credentials were supplied, both with a 401.
Why did my read only return ten rows?
Because Mailjet's pagination Limit defaults to 10 on every list endpoint. That is small enough to truncate almost any real read silently, including a statistics window longer than ten slices, and nothing about the response says it was cut short. Raise Limit explicitly on every lister, up to Mailjet's maximum of 1000, and page with Offset beyond that. Every lister node in this connector says so in its description, and the connector raises the limit itself on the pickers that populate node dropdowns.
Put Mailjet to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Mailjet is a product of its respective owner; Mattering is an independent platform.