Manage GetResponse contacts, campaigns, newsletters and autoresponders. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"getresponse": {
"url": "https://getresponse.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"getresponse": {
"type": "http",
"url": "https://getresponse.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your GetResponse API key.
Create one in GetResponse → Settings → API. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
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: the login page asks for your GetResponse API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the GetResponse connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
getresponse_get_account | read | Get account Get the authenticated GetResponse account profile (id, email, name, company, plan, timezone, etc.). REST: GET /accounts. |
getresponse_list_campaigns | read | List campaigns (lists) 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. |
getresponse_get_campaign | read | Get campaign (list) Get a single campaign (mailing list) by id, including subscription confirmation settings. REST: GET /campaigns/{campaignId}. |
getresponse_list_contacts | read | List contacts List/search contacts across the account. Paginated, with optional email/name/campaign filters, sort, and a fields selector. REST: GET /contacts. |
getresponse_get_contact | read | Get contact Get a single contact by id, including campaign membership, tags, custom field values and engagement scoring. REST: GET /contacts/{contactId}. |
getresponse_list_newsletters | read | List newsletters List newsletters (one-off email broadcasts). Paginated, with optional subject filter and sort. REST: GET /newsletters. |
getresponse_get_newsletter | read | Get newsletter Get a single newsletter (email broadcast) by id, including its status and send settings. REST: GET /newsletters/{newsletterId}. |
getresponse_list_autoresponders | read | List autoresponders List autoresponders (drip/cycle emails sent automatically on a schedule after subscription). Paginated. REST: GET /autoresponders. |
getresponse_list_tags | read | List tags List the account's tags (labels applied to contacts for segmentation). REST: GET /tags. |
getresponse_list_custom_fields | read | List custom fields List the account's custom field definitions (custom contact attributes) — id, name, type and values. REST: GET /custom-fields. |
getresponse_list_from_fields | read | List from-fields List the account's verified 'from' fields (sender name/email addresses usable when sending). REST: GET /from-fields. |
getresponse_create_contact | write | Create contact 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. |
getresponse_update_contact | write | Update contact Update an existing contact's mutable fields (name, tags, custom field values). Only the fields you supply are changed. REST: POST /contacts/{contactId}. |
getresponse_delete_contact | write | Delete contact Delete (remove) a contact from the account. This unsubscribes them and deletes their data. REST: DELETE /contacts/{contactId}. |
getresponse_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
getresponse_request_feature | Request a missing feature Tell usefulapi that the user needs something the GetResponse tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
getresponse_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED GetResponse tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
getresponse_cancel_subscription | Cancel the Pro subscription Cancel the caller's GetResponse Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run getresponse_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this GetResponse server only. Subscribe with getresponse_upgrade (it returns a Stripe Checkout link). Cancel any time with getresponse_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running getresponse_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by GetResponse. The server calls the GetResponse API with your own GetResponse access, so it sees only the data that your account can see.
The login page asks for your GetResponse API key. See Before you connect for where to find it.
No. 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: the login page asks for your GetResponse API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the GetResponse API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in GetResponse.
Yes, if you approve it. 3 of the 14 GetResponse tools can create or change data. The other 11 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this GetResponse server only. Run getresponse_usage_status to see how many calls you used.
Ask the AI to run getresponse_upgrade: it returns a Stripe Checkout link. To cancel, run getresponse_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with getresponse_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.