# MailBluster Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## MailBluster

Manage MailBluster leads, custom fields, products and orders from Muse.

- Record: https://musedirectory.ai/connector/mailbluster
- Category: Marketing & Ads
- Developer: usefulapi (https://usefulapi.io/mailbluster/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 3231ms, checked 2026-10-29T10:45:47Z
- Endpoint: https://mailbluster.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T08:01:30Z)
- Source: Found in the official MCP Registry (io.usefulapi/mailbluster) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fmailbluster

Connect to MailBluster to look up, create and update leads (contacts), custom fields, products and order records. Muse can help you manage your email marketing data and track customer orders without leaving your inbox.

Example request: "Add a new customer to my MailBluster list with their email and company name after they place an order."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use MailBluster to help me. It is a free service with an MCP server at https://mailbluster.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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 ha
- 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 fa
- 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}.

Screening checks:
- MCP handshake: pass (Answered in 1195ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mailbluster.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (13 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)