Work with eDesk support tickets, replies, internal notes, contacts and sales orders. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"edesk": {
"url": "https://edesk.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"edesk": {
"type": "http",
"url": "https://edesk.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your eDesk API token.
Create it at dashboard.edesk.com/api-token. The eDesk API is part of the Enterprise plan. The token acts with the permissions of the user who created it. Your token is used only to call the eDesk API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your eDesk API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
edesk_whoami | read | Who am I The eDesk user the API token belongs to: id, name, email, username, role and active flag. GET /whoami. |
edesk_list_users | read | List users (agents) 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 | read | 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 | read | List tag groups List the tag groups that organize ticket tags. GET /tag-groups. |
edesk_list_tags | read | 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 | read | List reply templates List saved reply templates (id, name, subject, body text, channels, usage). GET /templates. |
edesk_get_template | read | Get reply template One reply template by id. GET /templates/{id}. |
edesk_list_tickets | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | read | 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 | 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 internal 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 | Reply to customer 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_add_order_note | write | Add order note WRITE: add an internal note to a sales order (never sent to the customer). POST /order-notes. |
edesk_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
edesk_request_feature | Request a missing feature Tell usefulapi that the user needs something the eDesk tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
edesk_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED eDesk tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
edesk_cancel_subscription | Cancel the Pro subscription Cancel the caller's eDesk Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run edesk_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited |
Pro covers this eDesk server only. Subscribe with edesk_upgrade (it returns a Stripe Checkout link). Cancel any time with edesk_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running edesk_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by eDesk. The server calls the eDesk API with your own eDesk access, so it sees only the data that your account can see.
The login page asks for your eDesk API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your eDesk API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the eDesk API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in eDesk.
Yes, if you approve it. 4 of the 18 eDesk tools can create or change data. The other 14 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this eDesk server only. Run edesk_usage_status to see how many calls you used.
Ask the AI to run edesk_upgrade: it returns a Stripe Checkout link. To cancel, run edesk_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with edesk_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.