How to Use the Blip MCP in CrewAI

Q: Can multiple CrewAI agents use Blip tools simultaneously?

Yes, your agents can share access to tools like sendmessage and listthreads to coordinate their work. One agent can monitor the queue while another drafts the replies. This cooperative approach speeds up response times significantly.

Q: How do CrewAI agents handle complex Blip thread histories?

Your agents use getthreadmessages to retrieve the full chat history and store it in their shared memory. This allows the crew to maintain context across multiple turns. The resulting replies are highly accurate and aligned with previous messages.

Deploy autonomous agent teams using CrewAI to manage your Blip support queues, threads, and customer communications.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Blip MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative ticket resolution in CrewAI

This MCP Server lets your triage agent use the `list_tickets` tool to scan incoming customer issues and assign them to specialized team members. A separate responder agent then uses `get_ticket` to pull full details and draft solutions. Because your agents share memory, they remember previous interactions with the same customer. This prevents redundant questions and keeps support cohesive across different channels.

Autonomous thread monitoring and response

Using this MCP integration, the `list_threads` tool gives your monitoring agent a bird's-eye view of all active conversations. When a thread requires attention, the monitoring agent hands it off to a writer agent. That writer agent uses `get_thread_messages` to understand the context and `send_message` to reply. This entire cycle runs autonomously, keeping customer wait times close to zero.

Automated customer profile enrichment

The `get_contact` tool allows your research agent to pull customer profiles during live chats. If the agent finds missing details, it uses `create_contact` to update the record in real time. This keeps your customer database accurate without requiring human data entry. Your agents handle the entire lifecycle, from initial contact creation to eventual database cleanup.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

You can pass the Vinkius URL directly into the agent's mcps parameter during initialization. This instantly exposes all Blip tools to that specific agent. You can also filter tools to restrict access if needed.

Yes, your agents can share access to tools like send_message and list_threads to coordinate their work. One agent can monitor the queue while another drafts the replies. This cooperative approach speeds up response times significantly.

Your agents use get_thread_messages to retrieve the full chat history and store it in their shared memory. This allows the crew to maintain context across multiple turns. The resulting replies are highly accurate and aligned with previous messages.

Yes, you can use the advanced HTTP setup to filter tools before passing them to your crew. For example, you can allow a writer agent to use send_message while blocking it from using delete_contact. This keeps your operations secure and controlled.

All interactions between your agents and the Blip API run through Vinkius's secure, ephemeral sandbox. Your customer messages, contacts, and tickets are never exposed to external databases. This setup ensures strict data privacy and compliance with enterprise security standards.

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