get_accountGet AccountReturns general information about the signed-in Mailpro account.
The Mailpro MCP server lets Claude, ChatGPT and other assistants work with a Mailpro account: read campaigns and results, look up contacts, prepare lists and templates. The account owner signs in and decides what the assistant may do.
https://api.mailpro.com/mcpOne address for every assistant. Transport: Streamable HTTP. Sign-in: OAuth 2.1 with PKCE. There is no API key to copy.
1. Add the server in the assistant
In the assistant's settings, add a connector (remote MCP server) and paste the address above.
2. Sign in to Mailpro
The assistant opens a Mailpro page. Sign in with your Mailpro account: the assistant never sees your password.
3. Accept the rights
The page lists what the assistant asks for. Accept or refuse. The assistant is then listed in the app, under Settings → SMTP & API → AI Assistants (MCP).
Every tool works on the account of the signed-in user: no tool takes an account id. Names and descriptions are in English, as the assistant receives them.
get_accountGet Accountget_credit_balanceGet Credit Balanceget_api_usageGet API Usageget_sending_usageGet Sending Usagelist_campaignsList Campaignsget_campaignGet Campaign Detailsget_campaign_statisticsGet Campaign Statisticsget_campaign_bouncesGet Campaign Bouncesget_campaign_opensGet Campaign Opensget_campaign_clicksGet Campaign Clickscompare_campaignsCompare Campaign Performancelist_scheduled_sendsList Scheduled Sendsget_email_delivery_statusGet Email Delivery Statuslist_automationsList Automationssearch_contactsSearch Contactsfind_contact_by_emailFind Contact By Emailget_contactGet Contact Detailsget_contact_activityGet Contact Activitycreate_contactCreate Contactimport_contactsImport Contactsupdate_contactUpdate Contactunsubscribe_contactUnsubscribe Contactlist_suppressionsList Bounces and Unsubscribeslist_contact_listsList Contact Listsget_contact_listGet Contact Listcreate_contact_listCreate Contact Listadd_contact_to_listAdd Contact to Listremove_contact_from_listRemove Contact from Listlist_tagsList Tagscreate_tagCreate Tagadd_contact_tagAdd Tag to Contactremove_contact_tagRemove Tag from Contactlist_segmentsList Segmentscount_segment_contactsCount Segment Contactslist_custom_fieldsList Custom Fieldslist_email_templatesList Email Templatesget_email_templateGet Email Templatecreate_email_templateCreate Email Templateupdate_email_templateUpdate Email Templatelist_sender_emailsList Sender Addressesget_sender_authenticationGet Sender Authenticationget_send_settingsGet Send Settingssend_transactional_emailSend Transactional Emailsend_email_campaignSend Email Campaignsend_approved_requestSend Approved Requestget_send_requestGet Send Requestcancel_scheduled_email_campaignCancel Scheduled Email Campaignreschedule_email_campaignReschedule Email Campaignsend_transactional_smsSend Transactional SMSsend_sms_campaignSend SMS Campaigncancel_scheduled_smsCancel Scheduled SMSAn assistant can send an email, an SMS or a campaign from the account. The account owner decides how, for each connected assistant, in the app under Settings → SMTP & API → AI Assistants (MCP).
| Mode | How it works |
|---|---|
| With approval | The default. The assistant requests the send; nothing leaves. The owner sees the recipient, the sender, the subject and the content in the app and approves or refuses within 30 minutes. Once approved, the assistant sends it within one hour, once, with exactly the approved content. |
| Direct send | The send leaves at once, without approval. For an email or an SMS to one person, a daily limit applies per assistant: 100 emails and 20 SMS by default, changed by the owner. |
| SMS campaign | Always with approval, whatever the mode. |
| Suspend | One button in the app stops every send of every assistant at once. Reading keeps working. |
Sends use the account's email and SMS credits, like any other send. A request that is not approved in time expires: nothing is sent.
The server also gives the assistant two guides (resources) and three ready-made requests (prompts). They are fixed text: reading them uses no API request.
| Name | What it is |
|---|---|
mailpro://guide/getting-started | Guide: which tool to start with, how ids and paging work. |
mailpro://guide/deliverability | Guide: the rules that keep emails out of spam, and the tool that checks each one. |
analyze_last_campaign | Request: read the results of the latest campaign and explain them. |
compare_recent_campaigns | Request: compare the latest campaigns and show the trend. |
check_sender_setup | Request: check the sender addresses and their domain authentication. |
The assistant asks for rights when it connects, and the user sees them before accepting. A tool whose right was not granted answers with an error; nothing is done.
| Right | Allows |
|---|---|
account:read | View account credits, limits and subscription |
contacts:read | View contacts, lists, tags and segments |
contacts:write | Create and edit contacts, lists and tags |
email:read | View campaigns, delivery, opens, clicks and bounces |
email:templates:read | View email templates |
email:templates:write | Create and edit email templates |
email:send | Send emails on your behalf |
sms:send | Send SMS messages on your behalf |
sms:read | View SMS balance and history |
Removing access: in the app, under Settings → SMTP & API → AI Assistants (MCP), click Remove access. The assistant loses access within 20 minutes at most, the lifetime of a token.
| Limit | Value |
|---|---|
| API request quota | Every tool call counts against the account's API request quota, like a direct API call. The tool get_api_usage shows what is left. |
| Lists | 20 items per page by default, 50 at most. has_more says whether another page exists. |
| Rate | 300 requests per minute and per IP address on the MCP server. |
| Token | Valid for 20 minutes, renewed by the assistant without asking the user again. |
The server follows the MCP authorization specification: an MCP client finds everything from the server address.
| Step | Detail |
|---|---|
| No token | The server answers 401 with a WWW-Authenticate header that gives the address of its resource metadata. |
| Resource metadata | https://api.mailpro.com/mcp/.well-known/oauth-protected-resource (RFC 9728): authorization server and rights. |
| Authorization server | https://api.mailpro.com/oauth/.well-known/oauth-authorization-server (RFC 8414). |
| Client registration | Dynamic registration (RFC 7591) at the registration_endpoint of the authorization server. Public client, no secret. |
| Authorization | authorization_code with PKCE S256, and the resource parameter (RFC 8707) set to the server address. A token issued for the MCP server is not accepted by the Mailpro APIs when called directly. |
| Sessions | None: the server is stateless, each request carries its token. |
| Response | Meaning |
|---|---|
| 401 | Missing, invalid or expired token. The assistant signs in again or renews its token. |
| 429 | Too many requests in one minute. Wait and try again. |
| Tool error | The tool answers with a short message in English: item not found, right not granted, quota used up, or request refused by Mailpro. When a change is refused, nothing was changed. |