How to Use the eSputnik MCP in CrewAI

Q: Can I restrict which eSputnik tools a specific CrewAI agent uses?

Yes. Use MCPServerHTTP from crewai.mcp and apply a toolfilter. You can give your analyst agent read-only access while your action agent gets write permissions.

Deploy a CrewAI agent squad to run your eSputnik campaigns and monitor engagement autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect eSputnik MCP to CrewAI

Create your Vinkius account to connect eSputnik 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 eSputnik with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous engagement monitoring

The `list_unsubscribed` tool lets a dedicated monitor agent scan your eSputnik database for recent opt-outs. This agent runs quietly in the background, ensuring nobody slips through the cracks. Checking delivery rates happens through `get_message_status`. Your analyst agent polls this endpoint, reads the bounce data, and passes the findings to a moderator agent for list cleaning.

Specialized campaign execution

The `search_contacts` tool gives your researcher agent the ability to hunt down specific high-value targets by phone number. Once the target is verified, the agent shares that context in the crew's shared memory. Firing off the actual message is handled by an action agent using `send_smart_send`. Because CrewAI supports role-based specialization, the agent writing the copy isn't the same one executing the API call.

List management via MCP Server

The `list_groups` tool within the eSputnik MCP Server allows your crew to audit your entire segmentation strategy. A strategist agent pulls the active groups and decides if the current structure makes sense. Kicking off internal workflows relies on `trigger_event`. When your agents detect a specific pattern in the data, they fire an event back into the marketing system to start a predefined automation sequence.

Setup guide

Set up eSputnik 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 eSputnik tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent eSputnik 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="eSputnik Analyst",
        goal="Access and analyze eSputnik data via MCP.",
        backstory="Expert analyst with direct eSputnik access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent eSputnik 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 eSputnik. 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 eSputnik 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 eSputnik MCP in CrewAI

Install CrewAI with the tools extra. Pass the Vinkius URL directly into the `mcps` array on your Agent definition. The framework handles the rest.

Yes. Use `MCPServerHTTP` from `crewai.mcp` and apply a `tool_filter`. You can give your analyst agent read-only access while your action agent gets write permissions.

They use shared memory. If Agent A finds a contact, Agent B reads that context and sends the message without needing to run a second search.

The framework natively handles stdio, SSE, and Streamable HTTP. You just drop in the URL and CrewAI negotiates the connection.

Organization IDs and campaign metrics remain strictly confined to the V8 sandbox. Authentication is handled upstream by Vinkius, so your API keys never touch the local agent environment.

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