Bring Omnichannel Support
to AutoGen
Learn how to connect Dixa to AutoGen and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Dixa MCP Server?
Connect your Dixa account to any AI agent and take full control of your omnichannel customer service and team coordination workflows through natural conversation.
What you can do
- Conversation Orchestration — List and manage active support tickets programmatically, including retrieving detailed metadata and historical context
- Agent & Team Coordination — Assign conversations to yourself or specific team members and monitor agent availability in real-time to optimize response times
- Customer Profile Intelligence — Access and manage end-user (customer) profiles programmatically to maintain a high-fidelity record of contact information and interaction history
- Lifecycle Management — Programmatically create new support requests or mark existing conversations as resolved/closed to maintain a structured support pipeline
- Operational Monitoring — Check API connectivity and monitor active webhooks directly through your agent for reliable service operations
How it works
1. Subscribe to this server
2. Retrieve your API Token from the Dixa dashboard (Settings > Integrations > API Tokens)
3. Start managing your customer interactions from Claude, Cursor, or any MCP client
No more manual ticket shuffling or digging through agent lists in the portal. Your AI acts as your dedicated support strategist and CX coordinator.
Who is this for?
- Support Leads & Managers — instantly retrieve ticket summaries and reassign high-priority conversations using natural language commands
- Customer Success Teams — monitor customer profiles and interaction history without leaving your communication tools
- Operations Leads — verify system health and manage webhook configurations through simple AI queries
Built-in capabilities (12)
Claim a conversation
Add new support chat
Add new customer
Get agent details
Check API health
Get ticket info
Get event configs
List customer tickets
List Dixa customers
List active agents
List agent teams
Close a conversation
Why AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Dixa tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Dixa tools to solve complex tasks
- —
Role-based architecture lets you assign Dixa tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive Dixa tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes Dixa tool responses in an isolated environment
Dixa in AutoGen
Dixa and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dixa to AutoGen through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Dixa in AutoGen
The Dixa MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in AutoGen only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Dixa for AutoGen
Every tool call from AutoGen to the Dixa MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Dixa API Token?
Log in to Dixa, navigate to Settings > Integrations > API Tokens, and generate a new token for your integration.
Can I assign tickets to myself via AI?
Yes! Use the assign_to_self tool with a specific conversation ID to take ownership of a support ticket.
How do I check which agents are online?
The list_support_agents tool retrieves all agent profiles and their current status directly from the Dixa platform.
How does AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Dixa tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"