# Plumail MCP server

Source: https://glimind.com/server/mcp-registry%2Ffr.plumail%2Fplumail
Registry id: `mcp-registry/fr.plumail/plumail`
Status: live (checked 2026-10-26T19:13:50.362Z)

## Measurements (30 days)

- Uptime: 99.93%
- Checks: 4930
- Outages (90 days): 4

## Install

```json
{
  "mcpServers": {
    "plumail-mcp-server": {
      "type": "http",
      "url": "https://plumail.fr/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http plumail-mcp-server https://plumail.fr/api/mcp
```

## Tools (19)

- `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 
- `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 `unsu
- `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 b
- `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 no
- `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,
- `get_campaign_stats`: Status and figures for a campaign: recipients, sent, delivered, opened, clicked, bounced, complained. Rates are calculated on delivered messages, not on recipie
- `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
- `list_campaigns`: The workspace's campaigns, from newest to oldest, with their status: draft, scheduled, sending, or sent.
- `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 subscribe
- `list_suppression`: Suppressed addresses, with their reason: bounced, complained or manually suppressed (nothing goes to them), or unsubscribed (no more campaigns, automations, or 
- `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 
- `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. Wit
- `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 
- `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 
- `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
- `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 a
- `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
- `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 canno
- `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-bo

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.