How to Use the Dixa MCP in CrewAI

Q: How do CrewAI agents collaborate on Dixa conversations?

One agent can use listconversations to find open tickets, while another uses getconversationdetails to analyze the history and draft a response.

Deploy a collaborative CrewAI team to manage your Dixa support queue autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dixa MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous queue monitoring with CrewAI

The `list_conversations` tool feeds live Dixa ticket data to your CrewAI monitoring agent, which analyzes incoming issues for urgency. Once identified, a CrewAI coordinator agent delegates the Dixa ticket to a specialized agent for resolution. This collaborative setup uses `get_conversation_details` to pull Dixa ticket histories, giving your entire CrewAI team shared context. Because the CrewAI agents work in parallel, your Dixa queue gets sorted and prioritized without human intervention.

Collaborative agent assignment via MCP Server

The `assign_to_self` tool allows a CrewAI agent to claim a Dixa ticket on behalf of a human teammate based on their current workload. A CrewAI supervisor agent first queries `list_support_agents` to see which Dixa agents are active. After finding the right match, the CrewAI model assigns the Dixa ticket and notifies the team. This prevents Dixa tickets from sitting in unassigned queues while CrewAI agents are busy with other tasks.

Automated resolution and verification

The `resolve_conversation` MCP tool closes out resolved Dixa support tickets after your CrewAI quality-assurance agent verifies the customer's issue is fixed. The CrewAI QA agent checks the Dixa conversation log before allowing the resolution tool to run. If the connection drops during this process, the CrewAI team checks `get_connection_status` to diagnose the Dixa connection health. This keeps your autonomous CrewAI support workflows running reliably without silent Dixa failures.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

One agent can use `list_conversations` to find open tickets, while another uses `get_conversation_details` to analyze the history and draft a response.

Yes. You can filter the tools exposed to your crew, ensuring agents only access safe tools like `list_support_teams` while restricting destructive actions.

Your crew uses hierarchical execution where a manager agent reads the queue and uses `assign_to_self` to distribute tickets to specialized agents.

Yes. You can chain tasks together, such as looking up a user with `list_end_users` before calling `create_customer_profile` in the next step.

Vinkius hosts this MCP Server in an ephemeral, zero-trust sandbox. Your conversation logs and support agent details are processed entirely in memory and never cached or stored.

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