How to Use the Blueshift MCP in CrewAI

Q: Can I limit which Blueshift tools a CrewAI agent can use?

Yes, use MCPServerHTTP with a toolfilter to restrict access. This prevents a research agent from accidentally calling createupdatecustomer while allowing it to run getcampaignperformance.

Run multi-agent marketing crews using CrewAI to analyze Blueshift campaigns and update customer segments.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Blueshift MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Multi-Agent Campaigns with CrewAI

The `list_campaigns` and `get_campaign_detail` tools give your specialized agents deep access to your marketing data. Inside a CrewAI setup, you can have a "Research Agent" gather campaign metrics while an "Analyst Agent" evaluates the performance. They share memory and collaborate to produce a detailed strategy report without human intervention. This multi-agent coordination happens autonomously. By passing the MCP Server URL directly to your agents, they gain the ability to inspect active campaigns and suggest immediate optimizations.

Coordinate Customer Segment Updates

The `list_segments` and `create_update_customer` tools allow your crew to manage audience targeting dynamically. One agent can monitor user event history via `get_event_history` while another agent updates the customer profile. They work in sequence, passing data down the line to ensure your marketing segments are accurate. You configure this using CrewAI's sequential or hierarchical process models. The agents use shared memory to keep track of which profiles have been processed, preventing redundant tool calls.

Track Events and Catalog Items Autonomously

The `track_event` and `get_catalog_items` tools allow your autonomous agents to react to user behaviors and inventory changes. Your crew can monitor product availability and instantly log custom events when items go out of stock. This keeps your marketing platform perfectly aligned with your actual catalog status. For advanced setups, use the MCP helper classes from the CrewAI library. This lets you apply a `tool_filter` so your agents only access the specific tools they need for their roles.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

You can pass your Vinkius HTTP MCP URL directly into the agent's `mcps` parameter. The framework connects to the server and exposes all ten tools to that specific agent.

Yes, use `MCPServerHTTP` with a `tool_filter` to restrict access. This prevents a research agent from accidentally calling `create_update_customer` while allowing it to run `get_campaign_performance`.

Agents use CrewAI's shared memory system to pass context. If one agent calls `get_customer`, the retrieved profile details are available to the next agent in the crew.

Yes, CrewAI supports SSE, stdio, and Streamable HTTP transports. Vinkius manages the connection, so your crew can communicate with the server using standard HTTP protocols.

Your customer profiles, campaign histories, and event logs are protected by ephemeral, zero-trust environments. Vinkius handles authorization using a single endpoint token, ensuring your raw credentials never reach the CrewAI execution 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