Bring Ai Support
to Windsurf
Learn how to connect Desku.io to Windsurf and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Desku.io MCP Server?
Connect your Desku.io account to any AI agent and take full control of your customer support operations and helpdesk workflows through natural conversation.
What you can do
- Ticket Orchestration — List and manage support tickets programmatically, including updating statuses (open, pending, closed) and retrieving detailed metadata
- Conversation Intelligence — Access complete message history for any ticket to provide high-fidelity context for replies and internal notes
- Direct Engagement — Programmatically add new replies or internal collaborator notes to tickets to streamline customer resolutions
- Customer Lifecycle — Access detailed customer profiles and monitor their entire ticket history to maintain perfectly coordinated support journeys
- Agent Coordination — Retrieve directories of support staff to understand team availability and assignments directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Desku.io profile settings
3. Start managing your helpdesk and customer relationships from Claude, Cursor, or any MCP client
No more manual ticket searching or complex dashboard navigation. Your AI acts as your dedicated support engineer and CX coordinator.
Who is this for?
- Support Teams — instantly respond to high-priority tickets and summarize customer histories using natural language commands
- Customer Success Managers — monitor user profiles and track resolution times without leaving your communication tools
- Operations Leads — automate agent assignment tracking and manage customer data through simple AI queries
Built-in capabilities (9)
Reply to a ticket
Create a new ticket
Get customer details
Get ticket details
List support agents
List conversation history for a ticket
List support customers
io account. List support tickets
Update a ticket
Why Windsurf?
Windsurf's Cascade agent chains multiple Desku.io tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 9 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 9 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
Desku.io in Windsurf
Desku.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Desku.io to Windsurf 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 Desku.io in Windsurf
The Desku.io 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 9 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Windsurf 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
Desku.io for Windsurf
Every tool call from Windsurf to the Desku.io 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 Desku API Key?
Log in to Desku.io, click your profile picture, navigate to Profile Settings, and you will find your API Key at the bottom.
Can I add internal notes for other agents?
Yes! Use the create_conversation tool and specify that the message is an internal note to coordinate with your team privately.
How do I see who is assigned to a ticket?
The get_ticket tool retrieves complete metadata including the assigned agent ID and their current status.
How does Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.