Connect Plumail and your agent gets 19 tools, among them add_subscriber, add_suppression, create_campaign. It answers at https://plumail.fr/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 23 September 2026; the last check, on 6 November 2026, succeeded.
Manage a Plumail email workspace: subscribers, segments, campaigns, transactional sends and stats.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_subscriber | Adds or updates a subscriber. By default the person enters as PENDING and receives a confirmation email: that is double opt-in, and it protects the workspace's sending reputation. `double_opt_in: false` subscribes directly and must only be Inputs: email, firstName, lastName, tags, double_opt_in |
add_suppression | Adds an address to the workspace's suppression list. By default (`manual`), it will receive nothing further, neither campaigns nor individual emails; with `unsubscribe`, only campaigns, automations, and sends carrying `unsubscribe_url` are Inputs: email, reason |
create_campaign | Creates a DRAFT. Nothing is sent: you then need to call send_campaign, or send it from the Mailcheer workspace. Content is written in plain text in `text` — a blank line separates paragraphs, "#" at the start of a line makes a heading. Alwa Inputs: name, subject, text, preheader, from, kind |
erase_subscriber | Erases a person from the workspace at THEIR request (right to erasure): record, name, fields, proof of consent, tags. Statistics of campaigns already sent do not move; the suppression list is not touched. To stop someone receiving anything, Inputs: email |
get_account | Returns the workspace this key grants access to, its scopes, plan, remaining emails this month (queued sends included), when the counter resets, billing status, member and domain limits, sending domains (verified or not) and registered send |
get_campaign_stats | Status and figures for a campaign: recipients, sent, delivered, opened, clicked, bounced, complained. Rates are calculated on delivered messages, not on recipients. Every rate comes twice: open_rate and click_rate include bots (security gat Inputs: id |
get_email | Status of an email sent via send_email: sent, delivered, bounced, or complained. Amazon's delivery callback arrives a few seconds to a few minutes after sending — a "sent" status right after the call is normal. Inputs: id |
list_campaigns | The workspace's campaigns, from newest to oldest, with their status: draft, scheduled, sending, or sent. Inputs: limit, cursor, status |
list_subscribers | Lists the workspace's subscribers, page by page. Use `cursor` with the `next_cursor` value from the response to get the next page. `status` filters on subscribed, pending, unsubscribed, bounced, or complained. Inputs: limit, cursor, status, q, updated_since |
list_suppression | Suppressed addresses, with their reason: bounced, complained or manually suppressed (nothing goes to them), or unsubscribed (no more campaigns, automations, or sends carrying `unsubscribe_url`, but an individual email still reaches them). T Inputs: limit, cursor, email |
list_tags | The workspace's tags, with how many subscribers carry each one (`subscribers`) and, among them, the active ones (`subscribed`). Read this before tagging: reuse an existing name rather than creating a near-duplicate. |
preview_campaign_send | Read-only: nothing is sent. Returns exactly what send_campaign would do right now — would it go out (and if not, why), and how many people would receive it. With `to`, reports address by address who is kept and who is excluded, with the rea Inputs: id, to |
remove_subscriber | Unsubscribes an address and adds it to the workspace's suppression list: no more campaigns, automations, or sends carrying `unsubscribe_url`. The record is not deleted — that is what prevents the address from coming back on the next file im Inputs: email |
send_campaign | ⚠️ IRREVERSIBLE. Locks the recipient list and triggers sending to ALL active subscribers in the workspace — or, with `to`, only to the requested addresses that are active subscribers (never an unsubscribed or suppressed address). A sent ema Inputs: id, to |
send_email | Sends a single (transactional) email to one or more addresses. The sender must belong to a verified domain of the workspace — call get_account to see which ones. An address suppressed for a bounce, a complaint or by hand fails the entire ca Inputs: from, to, subject, html, text, replyTo |
tag_subscriber | Adds (`add`) and removes (`remove`) tags on ONE existing subscriber, and nothing else: no subscription, no confirmation email, no status touched. Prefer it to add_subscriber for changing tags: add_subscriber is a subscription and sends the Inputs: email, add, remove |
update_campaign | Edits a DRAFT: name, subject, preheader, kind, sender, content (`text`). Nothing is sent. Prefer it to create_campaign to rework a text: otherwise the old draft stays in the list. A scheduled, sending or sent campaign cannot be edited (409) Inputs: id, name, subject, text, preheader, from |
update_subscriber | Updates the first name (`first_name`), last name (`last_name`) and custom fields (`fields`, by technical key) of an existing subscriber. The email address cannot be changed: it is the identifier. Tags are managed with `tag_subscriber`. Unkn Inputs: email, first_name, last_name, fields |
verify_email | Verifies one or more addresses (up to 100) BEFORE writing to them, without sending anything: syntax, a domain that receives mail, a mailbox that already hard-bounced on Mailcheer, disposable or role mailboxes, and DNS signals of a dead mail Inputs: emails |
Every block below points at https://plumail.fr/api/mcp. Pick your client and copy.
claude mcp add --transport http plumail https://plumail.fr/api/mcp
{
"mcpServers": {
"plumail": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://plumail.fr/api/mcp"]
}
}
}{
"mcpServers": {
"plumail": {
"url": "https://plumail.fr/api/mcp"
}
}
}{
"servers": {
"plumail": {
"type": "http",
"url": "https://plumail.fr/api/mcp"
}
}
}{
"context_servers": {
"plumail": {
"url": "https://plumail.fr/api/mcp"
}
}
}{
"mcpServers": {
"plumail": {
"serverUrl": "https://plumail.fr/api/mcp"
}
}
}{
"mcpServers": {
"plumail": {
"url": "https://plumail.fr/api/mcp"
}
}
}name: Plumail
version: 0.0.1
schema: v1
mcpServers:
- name: Plumail
type: streamable-http
url: https://plumail.fr/api/mcp{
"mcpServers": {
"plumail": {
"httpUrl": "https://plumail.fr/api/mcp"
}
}
}{
"mcpServers": {
"plumail": {
"type": "http",
"url": "https://plumail.fr/api/mcp"
}
}
}{
"mcpServers": {
"plumail": {
"url": "https://plumail.fr/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fplumail.fr%2Fapi%2Fmcp&type=streamable_http&id=plumail&name=Plumail
It answered our last check on 6 November 2026 in 180 ms. Over 4 checks since 23 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by plumail.fr and served from plumail.fr, the vendor's own domain: https://plumail.fr/api/mcp.
19, as returned by the server's own tools/list on 9 November 2026: add_subscriber, add_suppression, create_campaign, erase_subscriber, get_account, get_campaign_stats, get_email, list_campaigns, and 11 more.
It answered our last check on 6 November 2026 in 180 ms. Over 4 checks since 23 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://plumail.fr/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: fr.plumail. Endpoint host: plumail.fr. ARD identifier: urn:air:fr.plumail:mcp:plumail.
First indexed 19 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.