Manage support tickets, customer replies, internal notes and sales orders in eDesk
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.
Try asking Muse: "Show me all open support tickets assigned to me and let me reply to the most recent one"
Source: Found in the official MCP Registry (io.usefulapi/edesk) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 3 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. 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.
https://edesk.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
eDesk MCP is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://edesk.usefulapi.io/mcpResponse time at the last check: 1534ms. Worked in 100% of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
edesk_whoamiThe eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami.edesk_list_usersList the eDesk users (support agents) with id, name, email, username, role and active flag. Use the ids as ticket owners. GET /users.edesk_list_channelsList 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_groupsList the tag groups that organize ticket tags. GET /tag-groups.edesk_list_tagsList 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_templatesList saved reply templates (id, name, subject, body text, channels, usage). GET /templates.edesk_get_templateOne reply template by id. GET /templates/{id}.edesk_list_ticketsList 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-updatededesk_get_ticketOne 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_messageOne 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_contactsSearch 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_ordersList 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_orderOne 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_notesList the internal notes attached to sales orders (id, sales order id, author, text, attachments). GET /order-notes.edesk_update_ticketWRITE: 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_noteWRITE: 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_ticketWRITE, 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 (customeedesk_add_order_noteWRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes.https://edesk.usefulapi.io/mcpNot 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.
At the last check (October 29, 2026, 09:16 UTC) the endpoint was working, answering in 1534ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 18 tools, including edesk_whoami, edesk_list_users, edesk_list_channels, edesk_list_tag_groups. For example, you could ask Muse: "Show me all open support tickets assigned to me and let me reply to the most recent one"
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/edesk)). If you build eDesk MCP, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/edesk-mcp"><img src="https://musedirectory.ai/badge/edesk-mcp.svg" alt="eDesk MCP on musedirectory.ai" width="236" height="40"></a>