eDesk MCP by usefulapi

io.usefulapi/edesk · v1.0.0

Work with eDesk support tickets, replies, internal notes, contacts and sales orders.

MCPremoteno credentialsE-commerceKnowledge & docsMessaging

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 18 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 18 tools · 14 read, 4 write (incl. delete/pay) · E-commerce, Knowledge & docs, Email

Test call edesk_whoami: needs a key: HTTP 401 (539 ms)

How the rating is made

Answers without login: +30
Speed of first answer: +10
Lists tools: +10
Tool descriptions: +15
Parameter descriptions: +10
Read/write annotations: +5
Safe test call: +8
More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL

https://edesk.usefulapi.io/mcp

Tools

18 tools listed at last check

edesk_whoami The eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami.
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_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_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_get_template One reply template by id. GET /templates/{id}.
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_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_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_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_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_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_list_order_notes List the internal notes attached to sales orders (id, sales order id, author, text, attachments). GET /order-notes.
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_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_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)
edesk_add_order_note WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.

Badge

Markdown for your README

[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/edesk.svg)](https://clawy.uk/mcp/s/io.usefulapi/edesk)

Repository · Website