eDesk MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://edesk.usefulapi.io/mcp

claude mcp add --transport http edesk https://edesk.usefulapi.io/mcp

{
  "mcpServers": {
    "edesk": {
      "url": "https://edesk.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "edesk": {
      "type": "http",
      "url": "https://edesk.usefulapi.io/mcp"
    }
  }
}

https://edesk.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 13 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 18 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 1743 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1743 个服务器的 93% 更新
• 基础检查结果等于或优于此分类中其他 1743 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{