Control your support inbox from Claude
miniDesk comes with its own MCP server built in. Hook up Claude Desktop, Cursor, or any client that speaks MCP, and your support queue becomes a conversation partner instead of a tab you have to keep open.
What the MCP server exposes
Your inbox becomes a collection of callable tools. The server can show open tickets, pull full conversation histories, query your knowledge base, compose replies, reassign threads, and mark tickets done. Whatever a human rep can do in the UI, an AI client can trigger through MCP, using identical permission scopes.
- list_tickets: view open threads, sort by urgency or wait time
- draft_reply: compose a response sourced from your docs and prior threads
- search_docs: surface the best matching document or earlier reply
- assign_team: hand a thread to the correct teammate
- resolve: mark a thread closed after sending the answer
Set it up in one step
Register miniDesk as an MCP server inside your client's config file. The server is hosted on our side, so there is zero local setup or infrastructure. Grab your API key from workspace settings plus your workspace slug and you are ready.
{
"mcpServers": {
"minidesk": {
"command": "npx",
"args": ["-y", "@minidesk/mcp@latest"],
"env": {
"MINIDESK_API_KEY": "md_live_your_key",
"MINIDESK_WORKSPACE": "your_workspace"
}
}
}
}What to ask after connecting
Once the config is in place, type questions about your queue in normal language. The server maps each request to the matching API endpoints and brings back the data.
- What issues came up most this month? Scans every thread and returns the top five recurring topics by count.
- Write drafts for all pending threads, then give me the queue. Produces a suggested reply for each open conversation and queues them for review.
- Which help doc should I rewrite to cut the most tickets? Correlates unsuccessful replies with your content and identifies the culprit page.
>Triage everything that came in today
conversations.list status: open since: 24h
12 conversations read, 9 tagged, 3 escalated to you
Why having MCP built in matters
Plenty of support products give you a REST API and call it a day. You are left to write the integration, deploy it somewhere, refresh tokens, and patch it whenever endpoints move. Our MCP server is part of the app itself. It uses the same auth, ships in the same release, and runs on our infrastructure. Drop the config in and start asking questions. Zero glue code, nothing to deploy, no webhooks to chase down.
One price. All of customer support.
Start free, no card. When you upgrade, every feature is included, rather than a starting point with a list of add-ons to buy.