Bring Omnichannel Support
to Claude Desktop
Learn how to connect Deskpro 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 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 Claude Desktop?
Claude Desktop is the definitive way to connect Deskpro 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
Deskpro in Claude Desktop
Deskpro and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Deskpro 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 Deskpro in Claude Desktop
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 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
Deskpro for Claude Desktop
Every tool call from Claude Desktop 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.
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.