How to Use the GetResponse MCP in CrewAI

Q: How do I connect CrewAI to the GetResponse MCP Server?

You pass the Vinkius endpoint directly into your agent's mcps array. CrewAI handles the HTTP transport automatically.

Q: Can I restrict which GetResponse tools my CrewAI agents use?

Yes. Use MCPServerHTTP and configure a toolfilter. You can give your analyst agent access to getlistdetails while strictly denying it access to removesubscriber.

Q: How do multiple CrewAI agents share GetResponse subscriber data?

CrewAI uses shared memory. If Agent A runs listcontactfields, Agent B can read those field IDs from memory to properly format a new subscriber payload.

Q: Can a CrewAI agent verify GetResponse landing pages?

Yes. An agent can execute listpublishedpages, read the active URLs, and cross-reference them against your internal marketing calendar to find discrepancies.

Deploy autonomous marketing crews to manage GetResponse lists and subscribers with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GetResponse MCP to CrewAI

Create your Vinkius account to connect GetResponse to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GetResponse with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinate specialized marketing agents

CrewAI thrives on division of labor. You can assign one agent to act as a data analyst and another as a campaign manager. The analyst uses `list_email_contacts` to pull recent subscribers and assess their engagement levels. Once the analyst builds a report, it passes the context to the manager agent. The manager then uses `list_marketing_lists` to decide which new campaigns to spin up. The agents talk to each other and execute MCP Server tools without your intervention.

Build an autonomous lead pipeline with CrewAI

You can automate your entire intake process. When a new lead hits your system, a researcher agent grabs the email and runs `find_contact_by_email`. If the user exists, it pulls their history using `get_contact_details`. An action agent takes that history and decides whether to update their tags or drop them into a new flow. If it is a brand new lead, the agent immediately executes `add_new_subscriber`. The crew handles the logic while you focus on strategy.

Monitor GetResponse health via the MCP Server

Marketing systems need constant supervision. You can spin up a monitor agent that runs on a cron job. It calls `get_api_status` to ensure the GetResponse connection is live and active. Next, it pulls `list_published_pages` and `list_active_webhooks` to verify your funnel infrastructure is intact. If the agent detects a missing webhook or a downed page, it escalates the issue to a human moderator.

Setup guide

Set up GetResponse MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke GetResponse tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="GetResponse Analyst",
    goal="Access and analyze GetResponse data via MCP.",
    backstory="Expert analyst with direct GetResponse access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent GetResponse transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="GetResponse Analyst",
        goal="Access and analyze GetResponse data via MCP.",
        backstory="Expert analyst with direct GetResponse access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent GetResponse transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GetResponse. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect GetResponse now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about GetResponse MCP in CrewAI

You pass the Vinkius endpoint directly into your agent's `mcps` array. CrewAI handles the HTTP transport automatically.

Yes. Use `MCPServerHTTP` and configure a `tool_filter`. You can give your analyst agent access to `get_list_details` while strictly denying it access to `remove_subscriber`.

CrewAI uses shared memory. If Agent A runs `list_contact_fields`, Agent B can read those field IDs from memory to properly format a new subscriber payload.

Yes. An agent can execute `list_published_pages`, read the active URLs, and cross-reference them against your internal marketing calendar to find discrepancies.

The tool accesses personally identifiable information like emails and names via `get_contact_details`. Vinkius handles this by running the operation in a stateless, ephemeral sandbox. No PII is logged, stored, or cached on the server layer.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript