Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
MailBluster MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
13
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage MailBluster leads, custom fields, products and orders: look up, add and update records.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mailbluster-mcp-by-usefulapi https://mailbluster.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# mailbluster_list_fields, mailbluster_create_field, mailbluster_get_lead and 10 more
MailBluster MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mailbluster-mcp-by-usefulapi https://mailbluster.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| field_label | string | yes | Display label, e.g. Gender. |
| field_merge_tag | string | yes | Merge tag, e.g. gender. |
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)}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | The lead's email address (preferred). | |
| lead_hash | string | no | Alternative to email: the 32-character MD5 hex of the lowercased email. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Email address. | |
| first_name | string | no | — |
| last_name | string | no | — |
| fields | object | no | Custom field values keyed by the field's MERGE TAG (see mailbluster_list_fields), e.g. {"company": "Pied Piper"}. |
| timezone | string | no | IANA timezone, e.g. America/Los_Angeles. |
| ip_address | string | no | Lead's IP address; MailBluster derives country/city/timezone from it. |
| subscribed | boolean | no | Default false. true only with the lead's consent to receive email. |
| tags | array | no | Tag names to attach (created if missing). |
| overwrite_existing | boolean | no | Default false. true overwrites an existing lead with the same email. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Current email of the lead to update (preferred). | |
| lead_hash | string | no | Alternative to email: the 32-character MD5 hex of the lowercased current email. |
| new_email | string | no | Change the lead's email address to this. |
| first_name | string | no | — |
| last_name | string | no | — |
| fields | object | no | Custom field values keyed by the field's MERGE TAG (see mailbluster_list_fields), e.g. {"company": "Pied Piper"}. |
| timezone | string | no | — |
| ip_address | string | no | — |
| subscribed | boolean | no | Only pass to change the subscription. true only with the lead's consent. |
| add_tags | array | no | Tag names to attach (created if missing). Applied before remove_tags. |
| remove_tags | array | no | Tag names to detach. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_no | integer | no | Page number, from 1 (default 1). Pass the previous reply's meta.nextPageNo. |
| per_page | integer | no | Results per page, 1-100 (MailBluster default 10). |
Get one product record by the id you registered it under. GET /products/{product_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | Product id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | Your unique product id. |
| name | string | yes | Product name. |
WRITE: rename a product record. PUT /products/{product_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | Product id. |
| name | string | yes | New product name. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page_no | integer | no | Page number, from 1 (default 1). Pass the previous reply's meta.nextPageNo. |
| per_page | integer | no | Results per page, 1-100 (MailBluster default 10). |
Get one order record by the id it was created with. GET /orders/{order_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Order id. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Your unique order id. |
| customer | object | yes | — |
| campaign_id | integer | no | Id of the campaign that led to the order, if any. |
| currency | string | yes | ISO currency code, e.g. USD. |
| total_price | number | yes | Order total, e.g. 10.64. |
| items | array | yes | Ordered products. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_id | string | yes | Order id. |
| campaign_id | integer | no | — |
| currency | string | no | ISO currency code, e.g. USD. |
| total_price | number | no | New order total. |
| items | array | no | New complete item list; replaces the previous items. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MailBluster MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MailBluster MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.