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" } }}