Bring Omnichannel Support
to Cursor
Learn how to connect Dixa to Cursor 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 Cursor?
Cursor's Agent mode turns Dixa into an in-editor superpower. Ask Cursor to generate code using live data from Dixa and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Dixa in Cursor
Dixa and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dixa to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.