Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Getresponse 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.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage GetResponse contacts, campaigns, newsletters and autoresponders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http getresponse-mcp https://getresponse.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# getresponse_get_account, getresponse_list_campaigns, getresponse_get_campaign and 11 more
Getresponse 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 getresponse-mcp https://getresponse.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
14 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.
Get the authenticated GetResponse account profile (id, email, name, company, plan, timezone, etc.). REST: GET /accounts.
No parameter schema on file.
List the account's campaigns — GetResponse's name for mailing lists a contact can subscribe to. Paginated. Optional name filter and sort. REST: GET /campaigns.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Filter by campaign (list) name substring (→ query[name]). |
| sortName | string | no | Sort by campaign name ASC/DESC (→ sort[name]). |
| sortCreatedOn | string | no | Sort by created date ASC/DESC (→ sort[createdOn]). |
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
Get a single campaign (mailing list) by id, including subscription confirmation settings. REST: GET /campaigns/{campaignId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaignId | string | yes | The campaign (list) id — the alphanumeric token, not the numeric id. |
List/search contacts across the account. Paginated, with optional email/name/campaign filters, sort, and a fields selector. REST: GET /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | no | Filter by email substring (→ query[email]). | |
| name | string | no | Filter by name substring (→ query[name]). |
| campaignId | string | no | Restrict to contacts in this campaign (list) id (→ query[campaignId]). |
| sortEmail | string | no | Sort by email ASC/DESC (→ sort[email]). |
| sortCreatedOn | string | no | Sort by created date ASC/DESC (→ sort[createdOn]). |
| fields | string | no | Comma-separated list of fields to return, e.g. "name,email" (GetResponse fields). |
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
Get a single contact by id, including campaign membership, tags, custom field values and engagement scoring. REST: GET /contacts/{contactId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactId | string | yes | The contact id. |
| fields | string | no | Comma-separated list of fields to return, e.g. "name,email" (GetResponse fields). |
List newsletters (one-off email broadcasts). Paginated, with optional subject filter and sort. REST: GET /newsletters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | no | Filter by subject substring (→ query[subject]). |
| sortCreatedOn | string | no | Sort by created date ASC/DESC (→ sort[createdOn]). |
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
Get a single newsletter (email broadcast) by id, including its status and send settings. REST: GET /newsletters/{newsletterId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| newsletterId | string | yes | The newsletter id. |
List autoresponders (drip/cycle emails sent automatically on a schedule after subscription). Paginated. REST: GET /autoresponders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
List the account's tags (labels applied to contacts for segmentation). REST: GET /tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
List the account's custom field definitions (custom contact attributes) — id, name, type and values. REST: GET /custom-fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
List the account's verified 'from' fields (sender name/email addresses usable when sending). REST: GET /from-fields.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | 1-based page number (pagination). |
| perPage | integer | no | Records per page (GetResponse perPage; default 100, max 1000). |
Add a contact to a campaign (mailing list). GetResponse processes this asynchronously and returns HTTP 202 (queued) with no body — the contact appears in the list within a few minutes. REST: POST /contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Contact email address (required). | |
| campaignId | string | yes | The campaign (list) id to add the contact to (required). |
| name | string | no | Contact name (defaults to 'Friend' if omitted). |
| dayOfCycle | integer | no | Autoresponder cycle day to place the contact on (→ dayOfCycle). |
| tags | array | no | Array of tag ids to apply to the contact. |
| note | string | no | A free-text note to attach to the contact. |
| ipAddress | string | no | Contact IP address, used by GetResponse for geolocation. |
Update an existing contact's mutable fields (name, tags, custom field values). Only the fields you supply are changed. REST: POST /contacts/{contactId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactId | string | yes | The contact id to update. |
| name | string | no | New contact name. |
| tags | array | no | Array of tag ids to set on the contact. |
| customFieldValues | array | no | Custom field values to set (each { customFieldId, value:[...] }). |
Delete (remove) a contact from the account. This unsubscribes them and deletes their data. REST: DELETE /contacts/{contactId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| contactId | string | yes | The contact id to delete. |
| messageId | string | no | Optional id of the message this deletion is attributed to (→ query[messageId]). |
| ipAddress | string | no | Optional IP address to record for the deletion (→ query[ipAddress]). |
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 Getresponse 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.11.1.
1.11.1
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 Getresponse 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.