Bring Omnichannel Support
to Claude Desktop
Learn how to connect Dixa to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Dixa to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Dixa in Claude Desktop
Dixa and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dixa to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.