Bring Omnichannel Support
to Cursor
Learn how to connect Deskpro 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 Deskpro MCP Server?
Connect your Deskpro helpdesk to any AI agent and take full control of your customer support and internal help center workflows through natural conversation.
What you can do
- Ticket Orchestration — List and manage active and archived support tickets programmatically, including monitoring message history and updating priorities in real-time
- User & Organization Intelligence — Access complete profiles for end-users and organizations to maintain high-fidelity records of customer relationships and account status
- Knowledgebase Architecture — Access and retrieve content from your help center articles programmatically to coordinate information delivery and self-service support
- Staff Coordination — Retrieve directories of support agents and administrators to understand team assignments and coordinate complex support routing
- Operational Monitoring — Check API health status, manage outbound webhooks, and monitor account metadata directly through your agent for reliable service operations
How it works
1. Subscribe to this server
2. Retrieve your API Key and Instance URL from your Deskpro Admin Portal (Apps & Integrations > API Keys)
3. Start managing your support pipeline from Claude, Cursor, or any MCP client
No more manual ticket shuffling or digging through help center folders. Your AI acts as your dedicated support operations and CX coordinator.
Who is this for?
- Support Leads & Managers — instantly summarize ticket histories and reassign high-priority cases using natural language commands
- Customer Success Teams — monitor user profiles and organization health without leaving your communication tools
- Operations Leads — automate knowledgebase access and verify system connectivity through simple AI queries
Built-in capabilities (12)
Verify Deskpro API connectivity
Requires a subject, person email, and initial message. Open a new support ticket
Get details for a KB article
Get details for a specific ticket
Get details for a specific user
List active webhooks
List helpdesk staff (agents)
Supports filtering by status and department. List helpdesk tickets
List end-users
List knowledgebase articles
List user organizations
Modify an existing ticket
Why Cursor?
Cursor's Agent mode turns Deskpro into an in-editor superpower. Ask Cursor to generate code using live data from Deskpro 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
Deskpro in Cursor
Deskpro and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Deskpro 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 Deskpro in Cursor
The Deskpro 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
Deskpro for Cursor
Every tool call from Cursor to the Deskpro 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 Deskpro API Key?
Log in as an Admin, navigate to Apps & Integrations > API Keys, and click Add to generate a new key for your instance.
Can the agent update ticket priorities?
Yes! The update_ticket_properties tool allows the agent to modify status, urgency, and specific metadata of any support request.
Does it support reading internal articles?
Absolutely. Use the get_article_content tool with an article ID to retrieve the full text and metadata for your help center content.
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.