How to Use the Dixa MCP in CrewAI

Q: Does this Dixa integration support CrewAI shared memory?

Yes. When an agent pulls conversation details using getconversationdetails, that context is stored in CrewAI's short-term memory, allowing other agents in the crew to reference it during the same execution cycle.

Run autonomous CrewAI agent teams that monitor support queues, track agent performance, and route tickets inside your Dixa setup.

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

Build autonomous triage crews with this MCP Server

The Dixa MCP server gives your CrewAI agents direct access to support queues and live ticket lists to automate your triage work. A dispatcher agent can run `list_open_support_tickets` to grab unassigned customer issues, while an analyzer agent uses `get_conversation_details` to inspect the actual thread. This setup lets your crew categorize incoming issues and assign priorities without a human clicking through a dashboard. You can also set up a supervisor agent that monitors queue depths using `list_service_queues`. When a queue backs up, the agent flags the bottleneck and coordinates with other agents to distribute the load. It is a direct way to handle spike periods before your SLA metrics start slipping.

Track team availability and performance live

This integration provides tools like `quick_agent_presence_audit` and `get_agent_profile` so your CrewAI agents can monitor team availability in real time. Your monitoring agent checks who is online and active, matching current queue demands against available staff. If a tier-2 agent goes offline, your crew instantly knows and adjusts routing tasks. By using `list_service_agents` alongside `list_support_teams`, your agents map out which teams have the capacity to take on complex escalations. You get an objective, live view of your support floor operations without manual check-ins or constant status updates.

Auto-escalate complex tickets using keyword searches

The server exposes `search_conversations_by_subject` and `list_customer_conversations` to let your agents hunt down related historical customer issues. When a high-priority ticket hits the queue, an escalation agent searches for past threads with similar subjects to find previous solutions. Your crew pulls the historical context and drafts a response based on what worked before. Once the agent verifies the solution, it uses `get_service_account_metadata` to check account limits before pushing automated updates. This keeps your automated workflows running within safe operational boundaries while keeping customer response times under five minutes.

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

Pass the Vinkius SSE or HTTP URL directly into your agent's `mcps` list when initializing your crew. For advanced setups, use `MCPServerHTTP` from the `crewai.mcp` package to filter which tools your agents can access.

No, this MCP server is read-only and designed for monitoring, auditing, and searching. Your agents can read conversations using `get_conversation_details` or check queues using `list_service_queues`, but they cannot modify tickets or change agent statuses.

Your agents execute tools sequentially or hierarchically depending on your crew's design. For instance, a researcher agent runs `search_conversations_by_subject` and passes the resulting data to a writer agent to draft a response.

Yes. When an agent pulls conversation details using `get_conversation_details`, that context is stored in CrewAI's short-term memory, allowing other agents in the crew to reference it during the same execution cycle.

This MCP server runs in a secure, isolated V8 sandbox on Vinkius, meaning your customer conversations, agent profiles, and presence data are never stored or logged. Your API tokens are managed securely through a single endpoint token, and all transit data is encrypted directly between your CrewAI runner and the Dixa API.

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