MailBluster MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.23.4Updated Nov 7, 2026

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hosted MailBluster connector that lets an assistant look up, add and update leads, custom fields, products and order records.

What you can do
  • Look up a single lead by email address and read its name, custom fields, timezone, subscription status and tags
  • Create and update leads, including subscription flag and tags
  • List and create custom lead fields with their merge tags
  • List, get, create and rename product records used for sales tracking
  • List, get, create and update order records, including campaign, currency, total and line items
  • Check monthly tool-call usage, request a missing feature, or upgrade and cancel the paid plan
When to use it
Useful when you run email marketing or a small shop on MailBluster and want an assistant to check a contact, add or correct leads, or record and review product and order data without opening the dashboard.
Requirements
A remote MCP endpoint; no local install. Connect with the endpoint URL only and sign in through the server's OAuth login page using your own MailBluster credentials. No API key or Authorization header goes in the client config. A free plan allows 50 tool calls per month.
Before you install
Write tools change MailBluster data: creating fields alters the brand's data model, and creating or updating leads, products and orders modifies records. Setting subscribed to true subscribes a person to email, so only do it with their consent. Updating an order's items replaces all previous items. The server is a third-party host that receives your MailBluster credentials through its login page. Paid plans cost money and are billed through a payment link; cancellation gives no refund for the…

Installation

In SourceWeft

  1. Open MailBluster MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fmailbluster/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mailbluster-by-usefulapi": {
      "type": "http",
      "url": "https://mailbluster.usefulapi.io/mcp"
    }
  }
}

README

MailBluster MCP by usefulapi

Use MailBluster from Claude, Cursor, or any MCP client — look up and add leads, custom fields, products and orders for your e-commerce email marketing. Hosted, no local install: connect with your own MailBluster credentials.

Live endpoint: https://mailbluster.usefulapi.io/mcp · Homepage: https://usefulapi.io/mailbluster

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://mailbluster.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http mailbluster https://mailbluster.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "mailbluster": {      "url": "https://mailbluster.usefulapi.io/mcp"    }  }}

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, and the login page asks for your MailBluster credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/mailbluster/

Tools

ToolTypeWhat it does
mailbluster_list_fieldsreadList custom lead fields
mailbluster_create_fieldwriteCreate custom lead field
mailbluster_get_leadreadGet lead
mailbluster_create_leadwriteCreate lead
mailbluster_update_leadwriteUpdate lead
mailbluster_list_productsreadList products
mailbluster_get_productreadGet product
mailbluster_create_productwriteCreate product
mailbluster_update_productwriteUpdate product
mailbluster_list_ordersreadList orders
mailbluster_get_orderreadGet order
mailbluster_create_orderwriteCreate order record
mailbluster_update_orderwriteUpdate order record
mailbluster_usage_statusmetaUsage status (free-tier meter)
mailbluster_request_featuremetaRequest a missing feature
mailbluster_upgrademetaUpgrade to Pro or Pro+
mailbluster_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with mailbluster_upgrade (it returns a Stripe Checkout link). Cancel any time with mailbluster_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running mailbluster_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by MailBluster.

Source: servers/mailbluster/README.md at commit 4046075

Tools

13

mailbluster_list_fields

List custom lead 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.

Takes no parameters.

mailbluster_create_field

Create custom lead 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.

Parametersfield_labelrequiredfield_merge_tagrequired

mailbluster_get_lead

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)}.

Parametersemaillead_hash

mailbluster_create_lead

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 on its own. No email is sent by this tool (double opt-in is not offered). If the lead already exists the call fails unless overwrite_existing=true, which replaces the stored data (then `subscribed` must be given explicitly). POST /leads.

Parameterstagsemailrequiredfieldstimezonelast_namefirst_nameip_addresssubscribedoverwrite_existing

mailbluster_update_lead

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 receive email from this brand (the user is responsible for lawful consent); this server never subscribes anyone on its own. PUT /leads/{md5(email)}.

Parametersemailfieldsadd_tagstimezonelast_namelead_hashnew_emailfirst_nameip_addresssubscribedremove_tags

mailbluster_list_products

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.

Parameterspage_noper_page

mailbluster_get_product

Get product

Get one product record by the id you registered it under. GET /products/{product_id}.

Parametersproduct_idrequired

mailbluster_create_product

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.

Parametersnamerequiredproduct_idrequired

mailbluster_update_product

Update product

WRITE: rename a product record. PUT /products/{product_id}.

Parametersnamerequiredproduct_idrequired

mailbluster_list_orders

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.

Parameterspage_noper_page

mailbluster_get_order

Get order

Get one order record by the id it was created with. GET /orders/{order_id}.

Parametersorder_idrequired

mailbluster_create_order

Create order record

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 customer has consented to email. For a customer who already exists, the value may replace their stored subscription state. 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 on its own. POST /orders.

Parametersitemsrequiredcurrencyrequiredcustomerrequiredorder_idrequiredcampaign_idtotal_pricerequired

mailbluster_update_order

Update order record

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}.

Parametersitemscurrencyorder_idrequiredcampaign_idtotal_price

Version history

19
  1. v1.23.4LatestNov 7, 2026
  2. v1.22.3Nov 5, 2026
  3. v1.22.2Nov 5, 2026
  4. v1.22.1Nov 4, 2026
  5. v1.22.0Nov 3, 2026
  6. v1.21.1Nov 3, 2026
  7. v1.20.0Nov 1, 2026
  8. v1.18.0Oct 31, 2026
  9. v1.17.0Oct 31, 2026
  10. v1.16.2Oct 30, 2026
  11. v1.16.0Oct 30, 2026
  12. v1.11.0Oct 26, 2026
  13. v1.8.3Oct 25, 2026
  14. v1.8.0Oct 25, 2026
  15. v1.7.0Oct 24, 2026
  16. v1.4.0Oct 23, 2026
  17. v1.3.4Oct 22, 2026
  18. v1.3.3Oct 21, 2026
  19. v1.0.0Oct 12, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations