io.usefulapi由 usefulapi.io 发布官方发布者v1.23.3更新于 Nov 7, 2026
Work with Enchant help desk tickets: list, read, reply, add notes and labels, manage customers.
发布方自己的服务：Ably MCP by usefulapi
托管的 Enchant 客服工单服务器，让助手列出、读取、回复并管理工单、客户和客服人员。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.usefulapi%2Fenchant/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"enchant-by-usefulapi": {
"type": "http",
"url": "https://enchant.usefulapi.io/mcp"
}
}
}Use Enchant from Claude, Cursor, or any MCP client — tickets, replies, notes, labels and customers. Hosted, no local install: connect with your own Enchant credentials.
Live endpoint: https://enchant.usefulapi.io/mcp · Homepage: https://usefulapi.io/enchant
https://enchant.usefulapi.io/mcp.claude mcp add --transport http enchant https://enchant.usefulapi.io/mcp, then run /mcp to log in.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, and the login page asks for your Enchant credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/enchant/
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with enchant_upgrade (it returns a Stripe Checkout link). Cancel any time with enchant_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running enchant_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Enchant.
来源：servers/enchant/README.md，提交 4046075
List tickets
List and filter tickets (newest first by default). Enchant REST: GET /tickets. Use user_ids ["null"] for unassigned tickets. Each result has a short summary; use enchant_get_ticket for messages.
idspagesortspamcounttrashtypesstatesper_pageuser_idsinbox_idslabel_ids另有 2 个Get ticket
Get one ticket by id. Embed related data with `embed`: messages (the conversation: replies and notes), customer, user, inbox, labels. Each embedded type costs 1 extra rate-limit credit. Enchant REST: GET /tickets/{id}.
id必填embedList users (agents)
List the help desk users (agents): id, name, email. Use the ids to assign tickets and to author replies and notes. Enchant REST: GET /users.
pageper_pageList customers
List customers, or find one by contact: set contact_type and contact_value (for example email + an address). Enchant REST: GET /customers.
pagecountper_pagecontact_typecontact_valuesince_created_atGet customer
Get one customer by id, with the contacts (emails, phones, Twitter names). Enchant REST: GET /customers/{id}.
id必填Get attachment
Get the metadata of an attachment (name, size, MIME type) by id; attachment ids appear in ticket messages. Enchant REST: GET /attachments/{id}.
id必填Create ticket
WRITE: create an email ticket. Give customer_id, or a customer (matched by contact email, created if new). Optionally add the customer's first message with body (needs the customer's email). Enchant REST: POST /tickets.
bodysubject必填user_idcustomerinbox_idcustomer_idUpdate ticket
WRITE: change a ticket: state (open, hold, closed), assignee, inbox, subject, spam or trash (not both true). label_ids REPLACES all labels (empty array clears them); use enchant_add_ticket_labels to keep existing ones. Enchant REST: PATCH /tickets/{id}.
id必填spamstatetrashsubjectuser_idinbox_idlabel_idsAdd labels to ticket
WRITE: add one or more labels to a ticket without changing its other labels. Enchant REST: PUT /tickets/{id}/labels/{label_ids}.
id必填label_ids必填Remove labels from ticket
WRITE: remove one or more labels from a ticket; its other labels stay. Enchant REST: DELETE /tickets/{id}/labels/{label_ids}.
id必填label_ids必填Reply to customer
WRITE: send an outbound reply on a ticket. This SENDS A REAL EMAIL to the customer address in `to`. Use enchant_add_note for an internal note. Enchant REST: POST /tickets/{id}/messages (type reply, direction out).
id必填to必填body必填htmluser_id必填attachment_idsAdd internal note
WRITE: add an internal note to a ticket (not sent to the customer). Enchant REST: POST /tickets/{id}/messages (type note).
id必填body必填htmluser_id必填attachment_idsCreate customer
WRITE: create a customer with optional contacts (email, twitter, phone). Enchant REST: POST /customers.
summarycontactslast_namefirst_nameUpdate customer
WRITE: update a customer's name or summary. If `contacts` is given, it REPLACES the contact list; use enchant_add_customer_contact to add one. Enchant REST: PATCH /customers/{id}.
id必填summarycontactslast_namefirst_nameAdd customer contact
WRITE: add one contact (email, twitter or phone) to a customer. Enchant REST: POST /customers/{id}/contacts.
id必填type必填value必填Delete customer contact
WRITE, DELETES DATA: remove one contact from a customer. Enchant REST: DELETE /customers/{id}/contacts/{contact_id}.
id必填contact_id必填已满足适用检查项的 100%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
io.usefulapi官方发布者
面向 Ably 实时消息的托管 MCP 服务器：查看频道历史、在线状态与占用情况，发布消息，并查看应用用量与配置。
io.usefulapi官方发布者
托管式只读 MCP 服务器，让助手查询 Woffu 公司的用户、劳动合同、部门和办公地点。
io.usefulapi官方发布者
面向 White Label Loyalty 的托管 MCP 服务器：浏览奖励、查看客户积分钱包与等级进度，并用积分购买奖励。
io.usefulapi官方发布者
托管的 Weekdone 连接器，让助手读取周报、团队、目标与 KPI，并新增报告条目、评论和 KPI 数值。
io.usefulapi官方发布者
托管式只读 MCP 服务器，让助手列出 WebinarKit 的网络研讨会、场次时间、系列、会议以及白标子账户。
{ "mcpServers": { "enchant": { "url": "https://enchant.usefulapi.io/mcp" } }}