Bring Omnichannel
to Cursor
Learn how to connect Daktela 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 Daktela MCP Server?
Connect your Daktela omnichannel contact center to any AI agent and simplify how you coordinate customer support, track communication history, and manage CRM records through natural conversation.
What you can do
- Ticket Lifecycle — Create, list, and query support tickets and cases to ensure customer issues are resolved promptly.
- Omnichannel Activities — Monitor real-time and past activities across calls, emails, and chats within your center.
- CRM Control — List and create contacts and accounts (companies) to maintain an organized customer directory.
- Call & Email History — Retrieve detailed logs of past phone interactions and email threads for audit and reporting.
- Team & Queue Coordination — List configured queues and system users to manage agent distribution effectively.
- Profile Oversight — Fetch your authenticated user profile and verify system configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Daktela Domain and Access Token (found in your user settings)
3. Start managing your omnichannel communications from Claude, Cursor, or any MCP client
Who is this for?
- Support Team Leads — quickly check ticket statuses and monitor queue volumes via simple AI commands.
- Customer Service Agents — create CRM contacts and log activities directly from the workspace.
- Operations Managers — verify call history and retrieve agent distribution metadata via the AI assistant.
Built-in capabilities (12)
Create a new CRM contact
Create a new ticket
Get current user information
Get details of a specific ticket
List CRM accounts
List recent activities in Daktela
List call history
List CRM contacts
List email history
List contact center queues
List support tickets
List Daktela users
Why Cursor?
Cursor's Agent mode turns Daktela into an in-editor superpower. Ask Cursor to generate code using live data from Daktela 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
Daktela in Cursor
Daktela and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Daktela 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 Daktela in Cursor
The Daktela 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
Daktela for Cursor
Every tool call from Cursor to the Daktela MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the open tickets in my Daktela account?
Yes! Use the list_tickets tool. Your agent will retrieve the complete directory of support cases, which you can then filter or summarize.
How do I create a new contact in the Daktela CRM?
Use the create_contact action. Provide the first name, last name, and optional email or phone number to register the person in your CRM database instantly.
Is it possible to list the history of past phone calls via AI?
Absolutely. Use the list_call_history query. The agent will retrieve a detailed log of past voice interactions, including participants and durations.
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.
