Read rapidmail lists, recipients, mailings and stats; add, update or unsubscribe one recipient. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"rapidmail": {
"url": "https://rapidmail.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"rapidmail": {
"type": "http",
"url": "https://rapidmail.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your API user and API password.
Create them in rapidmail under Settings › API (my.rapidmail.de) with Create new API access. These are separate API credentials, not your rapidmail login e-mail and password. They are used only to call the rapidmail API on your behalf and are never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API user and API password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
rapidmail_list_recipientlists | read | List recipient lists List the recipient lists (newsletter audiences) of the rapidmail account with id, name, description, whether unsubscribed recipients are blacklisted, and which is the default. Use the ids for recipients and mailing filters. GET /recipientlists. |
rapidmail_get_recipientlist | read | Get recipient list One recipient list by id. GET /recipientlists/{id}. |
rapidmail_get_recipientlist_activity_stats | read | Get recipient list activity stats Subscription activity of one recipient list between two dates (for example new subscriptions and unsubscriptions). The range may be at most one year, must not start before the list was created and must not lie in the future. GET /recipientlists/{id}/stats/activity. |
rapidmail_list_recipients | read | List recipients List the recipients (subscribers) of ONE recipient list, optionally filtered by e-mail address, external id or status. recipientlist_id is required. The long text fields (extrabig1-10) are only returned with include_extrabig. GET /recipients. |
rapidmail_get_recipient | read | Get recipient One recipient by id: e-mail, name, status, custom fields and timestamps. GET /recipients/{id}. |
rapidmail_create_recipient | write | Add recipient WRITE: add ONE recipient (subscriber) to a recipient list. By default double opt-in is used: the recipient is created with status 'new' and rapidmail sends ONE confirmation e-mail to that address; they only receive newsletters after confirming. Set double_opt_in=false only if you hold the person's documented consent: the recipient is then stored as 'active' and no e-mail is sent (refused if the address was unsubscribed before). If a deleted recipient with the same address exists it is re-activated; an existing address returns a conflict error. Never use for bulk imports. POST /recipients. |
rapidmail_update_recipient | write | Update recipient WRITE: partially update ONE recipient (only the fields you pass change): e-mail, name, custom fields. The status and the recipient list cannot be changed here, and no e-mail is sent. An e-mail address that already exists in the list returns a conflict error. PATCH /recipients/{id}. |
rapidmail_unsubscribe_recipient | write | Unsubscribe recipient WRITE: remove ONE recipient from their list. rapidmail only soft-deletes the record (status 'deleted', as if the person had unsubscribed) and the statistics count it as an unsubscription. No goodbye e-mail is sent. Single recipient only. DELETE /recipients/{id}. |
rapidmail_list_mailings | read | List mailings List newsletters (mailings) with status, subject, sender, send time, recipient count and recipient lists. Filter by status, recipient list, created / updated / sent date. Read only: mailings are never created, sent or scheduled by this server. GET /mailings. |
rapidmail_get_mailing | read | Get mailing One mailing by id: status, subject, sender, destinations (recipient lists), send time, size and attachments. GET /mailings/{id}. |
rapidmail_get_mailing_stats | read | Get mailing statistics Statistics of one sent mailing (opens, clicks, bounces, unsubscriptions and similar totals). GET /mailings/{id}/stats. |
rapidmail_list_mailing_activity | read | List mailing recipient activity The recipients a mailing went to and what each did (delivered, opened, clicked, bounced). Detailed event information is only available if the respective plugin is enabled in the rapidmail account. GET /mailings/{id}/stats/activity. |
rapidmail_get_mailing_recipient_activity | read | Get one recipient's activity in a mailing Delivery and engagement details of one recipient of one mailing. GET /mailings/{id}/stats/activity/{mailingrecipient_id}. |
rapidmail_list_mailing_folders | read | List mailing folders The folders used to organise mailings, with id and name. GET /mailings/folders. |
rapidmail_list_blacklist | read | List blacklist entries The account's blacklist: e-mail addresses, domains and patterns that never receive mailings, with their type, source and dates. GET /blacklist. |
rapidmail_list_transactional_emails | read | List transactional e-mails Transactional (SMTP) e-mails sent through the rapidmail account: sender, recipient, subject, status (queued, delivered, bounced...), delivery diagnostics and open/click counts. Metadata only, no message bodies. Filter by date, status, project or address. GET /trx/emails. |
rapidmail_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
rapidmail_request_feature | Request a missing feature Tell usefulapi that the user needs something the rapidmail tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
rapidmail_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED rapidmail tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
rapidmail_cancel_subscription | Cancel the Pro subscription Cancel the caller's rapidmail Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run rapidmail_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this rapidmail server only. Subscribe with rapidmail_upgrade (it returns a Stripe Checkout link). Cancel any time with rapidmail_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running rapidmail_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by rapidmail. The server calls the rapidmail API with your own rapidmail access, so it sees only the data that your account can see.
The login page asks for your API user and API password. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your API user and API password. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the rapidmail API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in rapidmail.
Yes, if you approve it. 3 of the 16 rapidmail tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this rapidmail server only. Run rapidmail_usage_status to see how many calls you used.
Ask the AI to run rapidmail_upgrade: it returns a Stripe Checkout link. To cancel, run rapidmail_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with rapidmail_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.