eDesk MCP by usefulapi is answering right now. Last checked 4 min ago. It exposes 18 tools. Last commit 10 Oct 2026.
Work with eDesk support tickets, replies, internal notes, contacts and sales orders.
Uptime history
28 hours of history
28 hours agonow
100.0%
Uptime 24h
92 of 92 checks
18
Tools
read from the server
132 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026
Nothing serious here today
Today is the operative word: we check eDesk MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add edesk --transport http https://edesk.usefulapi.io/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"edesk": {
"url": "https://edesk.usefulapi.io/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.edesk]
url = "https://edesk.usefulapi.io/mcp".cursor/mcp.json
{
"mcpServers": {
"edesk": {
"url": "https://edesk.usefulapi.io/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"edesk": {
"url": "https://edesk.usefulapi.io/mcp"
}
}
}Available tools 18
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
edesk
edesk_add_order_note
WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.
edesk_add_ticket_note
WRITE: add an internal note to a ticket. The note is for the team only and is never sent to the customer. POST /messages with type Note.
edesk_get_message
One ticket message or internal note by id (from a ticket's message ids): body, direction, type (Message or Note), author and attachments. GET /messages/{id}.
edesk_get_sales_order
One sales order by id with items, amounts, ship-to and bill-to addresses, tracking codes, delivery dates, the linked ticket id and order note ids. GET /sales-orders/{id}.
edesk_get_template
One reply template by id. GET /templates/{id}.
edesk_get_ticket
One ticket by id with its status, owner, tags, custom fields, linked sales order and the ids of its messages (read each with edesk_get_message). GET /tickets/{id}.
edesk_list_channels
List the sales channels connected to eDesk (Amazon, eBay, Shopify, email, ...) with id, type, name, country and currency. Use the ids to filter tickets and orders. GET /channels.
edesk_list_contacts
Search the contacts (customers) of the helpdesk by free text, email, name, phone number or consumer id. Returns id, channel, full name, email and phone. GET /contacts.
edesk_list_order_notes
List the internal notes attached to sales orders (id, sales order id, author, text, attachments). GET /order-notes.
edesk_list_sales_orders
List the marketplace/store orders that eDesk holds, with status, items, amounts, addresses, tracking codes and the linked ticket id. Filter by status, channel, contact, marketplace order id, id range and created/updated dates. GET /sales-orders.
edesk_list_tag_groups
List the tag groups that organize ticket tags. GET /tag-groups.
edesk_list_tags
List ticket tags with id, name, color, active flag and tag group id. Use the ids in edesk_update_ticket (tag_ids). GET /tags.
edesk_list_templates
List saved reply templates (id, name, subject, body text, channels, usage). GET /templates.
edesk_list_tickets
List support tickets from all channels with subject, type, status, channel, owner, contact, linked sales order id, tag ids, message ids, reply count and AI classification. Filter by status, type, channel, contact, owner, sales order, seller (marketplace) order id and last-updated date. GET /tickets.
edesk_list_users
List the eDesk users (support agents) with id, name, email, username, role and active flag. Use the ids as ticket owners. GET /users.
edesk_reply_to_ticket
WRITE, CUSTOMER-VISIBLE: send a reply on a ticket. eDesk queues it for delivery to the marketplace or email channel, so it cannot be recalled once queued. The audience is the channel's default: on a Mirakl channel it is the channel's "Default messages recipients" setting (customer, operator or both), and this API cannot choose recipients (use the eDesk reply box when they matter). Only call this when the user has approved the exact text and audience. If the call fails in transit, the reply may still be queued: check the ticket before retrying. Use edesk_add_ticket_note for an internal note. POST /messages with type Message.
edesk_update_ticket
WRITE: change a ticket's status, owner (assignee), tags or subject. Only the fields you pass are sent. tag_ids is sent as given: read the ticket first (tags_ids) and include the tags to keep. Nothing is sent to the customer. PUT /tickets/{id}.
edesk_whoami
The eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://edesk.usefulapi.io/mcp | streamable-http | answering | 127 ms | 4 min ago |
Alternatives to eDesk MCP by usefulapi
same job, measured the same wayEnchant MCP by usefulapi
by usefulapi
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
HappyFox MCP by usefulapi
by usefulapi
Triage HappyFox tickets, contacts and KB articles, run reports, and reply or add private notes.
Trengo MCP by usefulapi
by usefulapi
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
Eventzilla MCP by usefulapi
by usefulapi
Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales.
SupportBee MCP by usefulapi
by usefulapi
Read SupportBee tickets, replies and reports; reply, comment, label, assign and archive tickets.
Insightly MCP by usefulapi
by usefulapi
Read and write Insightly contacts, organisations, leads, opportunities, tasks and notes.
Freshdesk MCP by usefulapi
by usefulapi
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Humanitix MCP by usefulapi
by usefulapi
Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.
eDesk MCP by usefulapi — questions
Answers built from our own checks of this server.
What can eDesk MCP by usefulapi do?
It exposes 18 tools, read directly from the server on our last check. Among them: edesk_add_order_note, edesk_add_ticket_note, edesk_get_message, edesk_get_sales_order, edesk_get_template, edesk_get_ticket and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is eDesk MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 132 ms. The bar chart above shows every period we have measured.
How do I connect eDesk MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does eDesk MCP by usefulapi need an API key?
No. eDesk MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is eDesk MCP by usefulapi?
It answers our handshake in 132 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is eDesk MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.