MailBluster MCP by usefulapi

io.usefulapi/mailbluster · v1.0.0

Manage MailBluster leads, custom fields, products and orders: look up, add and update records.

MCPremoteno credentialsE-commerceCRM & salesEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 13 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 85/100

What it does: 13 tools · 6 read, 7 write (incl. delete/pay) · CRM & sales, E-commerce, Email

Test call mailbluster_list_fields: needs a key: HTTP 401 (1,081 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +10
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +7
Read/write annotations: +5
Safe test call: +8
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://mailbluster.usefulapi.io/mcp

Tools

13 tools listed at last check

mailbluster_list_fields List the brand's custom lead fields: id, label and merge tag. Use the merge tags as keys of `fields` when creating or updating leads. GET /fields.
mailbluster_create_field WRITE: create a custom lead field. The merge tag is the key used in lead `fields` and in email templates. Creating a field changes the brand's data model but sends nothing. POST /fields.
mailbluster_get_lead Get one lead by email address (the server computes the MD5 id MailBluster uses): name, custom fields, timezone, subscribed and opt-in status, tags, created/updated dates. MailBluster has no list-leads endpoint. GET /leads/{md5(email)}.
mailbluster_create_lead WRITE: add a lead (contact) to the brand. `subscribed` defaults to FALSE: the lead is stored but is not subscribed to email. Only set subscribed=true when the person has given consent to receive email from this brand (the user is responsible for lawful consent); this server never subscribes anyone o
mailbluster_update_lead WRITE: change an existing lead's name, custom fields, email, timezone, IP address, subscription flag or tags (send only what should change). `subscribed` is left alone unless you pass it; false unsubscribes the lead, true re-subscribes. Only set subscribed=true when the person has given consent to r
mailbluster_list_products List product records (id, name, dates) the brand has registered for e-commerce tracking. Paged: the reply's meta has total and nextPageNo (null on the last page). GET /products.
mailbluster_get_product Get one product record by the id you registered it under. GET /products/{product_id}.
mailbluster_create_product WRITE: register a product record (your own id plus a name) so orders can reference it. Sends nothing to anyone and charges nothing. POST /products.
mailbluster_update_product WRITE: rename a product record. PUT /products/{product_id}.
mailbluster_list_orders List order records (id, currency, total price, customer lead, campaign, line items). These are records kept in MailBluster for tracking; no payment is involved. Paged: see meta.nextPageNo. GET /orders.
mailbluster_get_order Get one order record by the id it was created with. GET /orders/{order_id}.
mailbluster_create_order WRITE: record an order (a tracking record: it does not take payment, charge a card or send email). The customer's email becomes a lead if none exists, and the lead's tags are merged. `customer.subscribed` is REQUIRED because MailBluster would otherwise default it to true: pass false unless the custo
mailbluster_update_order WRITE: change an order record's campaign, currency, total or items (send only what should change; `items`, when given, REPLACES all previous items). The customer cannot be changed here. No payment or email is involved. PUT /orders/{order_id}.

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/mailbluster.svg)](https://clawy.uk/mcp/s/io.usefulapi/mailbluster)

Repository · Website