# MailBluster MCP by usefulapi

> MailBluster MCP by usefulapi is an MCP server. Manage MailBluster leads, custom fields, products and orders: look up, add and update records. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/mailbluster/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/mailbluster
- **MCP Registry name:** io.usefulapi/mailbluster
- **Listing updated:** 2026-11-13

## About

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

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http mailbluster https://mailbluster.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://mailbluster.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "mailbluster": {
      "url": "https://mailbluster.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "mailbluster": {
      "type": "http",
      "url": "https://mailbluster.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "mailbluster": {
      "serverUrl": "https://mailbluster.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

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

## 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 subscribes anyone on its own. No email is sent by this tool (double opt-in is not offered). If the lead already exists 
- `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 receive email from this brand (the user is responsible for lawful consent); this server never subscri
- `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 customer has consented to email. For a customer who already exists, the value may replace their stored su
- `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}.

## FAQ

### How do I add MailBluster MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http mailbluster https://mailbluster.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/mailbluster-mcp-by-usefulapi
