# eDesk MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## eDesk MCP

Manage support tickets, customer replies, internal notes and sales orders in eDesk

- Record: https://musedirectory.ai/connector/edesk-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/edesk/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1534ms, checked 2026-10-29T09:16:10Z
- Endpoint: https://edesk.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:46:25Z)
- Source: Found in the official MCP Registry (io.usefulapi/edesk) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fedesk

Connect to eDesk helpdesk to read and manage support tickets across Amazon, eBay, Shopify and email channels. View customer contacts, sales orders, reply templates and internal notes. Update ticket status, assign owners and add replies.

Example request: "Show me all open support tickets assigned to me and let me reply to the most recent one"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use eDesk MCP to help me. It is a free service with an MCP server at https://edesk.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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 (custome
- edesk_add_order_note: WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.

Screening checks:
- MCP handshake: pass (Answered in 14ms)
- Domain against threat feeds (Cloudflare security DNS): pass (edesk.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (18 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)