How to connect GetResponse MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"getresponse": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"GETRESPONSE_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/mateuszkami/getresponse-mcp
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: github.com/mateuszkami/getresponse-mcp.
Does GetResponse MCP cost extra?
The GetResponse MCP server is community-built — free to run, but you still pay for your GetResponse subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your GetResponse account still needs whatever plan is required to access the data the MCP server queries.
- Trade-off: zero MCP cost, but no guarantee it'll keep working when GetResponse changes their UI or API.
GetResponse subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Free | Free | Free |
| Starter | $19 | $15.58 |
| Marketer | $59 | $48.38 |
| Creator | $69 | $56.58 |
| Enterprise (MAX) | Contact sales | — |
Source: getresponse.com/pricing. Scraped 2026-05-19.
GetResponse also publishes a REST API
GetResponse publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with GetResponse from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe GetResponse data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's GetResponse account
- Multi-account workflows without context-switching the GetResponse UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage GetResponse data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production GetResponse safe
Limits and gotchas
- Community MCP — not maintained by GetResponse. Check the README and last-update date before depending on it.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (unknown). Expect to configure that on first install.
- Rate limits: MCP calls count against your underlying GetResponse API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Limited agent integration despite API access. GetResponse has a community MCP server and documented public API, but lacks official MCP support, OpenAPI spec, and any native Claude or ChatGPT integrations. The absence of webhooks and structured output support makes it difficult to build reliable autonomous workflows.
Scored 2026-05-19 by Joonas (TMB).
GetResponse MCP & API FAQ
Is the GetResponse MCP server official?+
Can I use the GetResponse MCP with Cursor or Codex?+
Does GetResponse have a public API?+
Sources
- GetResponse official site: https://www.getresponse.com/
- MCP server page: https://github.com/mateuszkami/getresponse-mcp
- API docs: https://www.getresponse.com/api
- Pricing source: https://www.getresponse.com/pricing (scraped 2026-05-19)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

