GetResponse MCP by usefulapi
Manage GetResponse contacts, campaigns, newsletters and autoresponders.
- 1.11.1
- Version
- remote
- Transport
- 14
- Tools
Security review
Review passedReviewed 1h ago.
- tools: 14 tools scanned
- metadata: scanned
No findings.
Tools (14)
getresponse_get_account
Get the authenticated GetResponse account profile (id, email, name, company, plan, timezone, etc.). REST: GET /accounts.
getresponse_list_campaigns
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
Get a single campaign (mailing list) by id, including subscription confirmation settings. REST: GET /campaigns/{campaignId}.
getresponse_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
Get a single contact by id, including campaign membership, tags, custom field values and engagement scoring. REST: GET /contacts/{contactId}.
getresponse_list_newsletters
List newsletters (one-off email broadcasts). Paginated, with optional subject filter and sort. REST: GET /newsletters.
getresponse_get_newsletter
Get a single newsletter (email broadcast) by id, including its status and send settings. REST: GET /newsletters/{newsletterId}.
getresponse_list_autoresponders
List autoresponders (drip/cycle emails sent automatically on a schedule after subscription). Paginated. REST: GET /autoresponders.
getresponse_list_tags
List the account's tags (labels applied to contacts for segmentation). REST: GET /tags.
getresponse_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
List the account's verified 'from' fields (sender name/email addresses usable when sending). REST: GET /from-fields.
getresponse_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
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
Delete (remove) a contact from the account. This unsubscribes them and deletes their data. REST: DELETE /contacts/{contactId}.