io.usefulapi由 usefulapi.io 發布官方發布者v1.39.2更新於 Nov 14, 2026
Manage Re:amaze conversations, messages, contacts and help articles.
發布方自己的服務：Ably MCP by usefulapi
託管式 MCP 伺服器，讓助理讀取並管理 Re:amaze 的客服對話、訊息、聯絡人、說明中心文章與報表。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fre-amaze/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"re-amaze-by-usefulapi": {
"type": "http",
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
}Manage Re:amaze conversations, messages, contacts and help articles. Hosted, no local install.
Live endpoint: https://re-amaze.usefulapi.io/mcp · Homepage: https://usefulapi.io
https://re-amaze.usefulapi.io/mcp.claude mcp add --transport http re-amaze https://re-amaze.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 Re:amaze credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/re-amaze/
On first connect you'll paste your Re:amaze credentials. They are validated, stored per-user, and scoped to you — no keys in config files.
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.
Each paid plan covers this server only. Ask your AI to run re_amaze_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with re_amaze_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with re_amaze_upgrade before then undoes the cancel. Or write to [email protected].
MIT
來源：servers/re-amaze/README.md，提交 f22f848
List conversations
List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.
fortagpagesortfilterfor_idorigincategoryend_datestart_dateGet conversation
Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.
slug必填List messages
List messages. If `conversation` (a slug) is given, list that conversation's messages (GET /conversations/{slug}/messages); otherwise list messages across the brand (GET /messages). All other filters optional. Re:amaze REST.
tagpagefilteroriginincludesent_bycategoryend_datestart_dateconversationList contacts
List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.
pagefilterGet contact
Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.
identifier必填List articles
List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.
pagefilterGet article
Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.
slug必填List staff
List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.
pageList channels
List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.
pageGet channel
Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.
slug必填Report: volume
Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.
end_datestart_dateReport: response time
Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.
end_datestart_dateCreate conversation
Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.
statussubject必填assigneecategory必填tag_listuser_name必填recipientsuser_email必填message_body必填Reply to conversation
Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.
body必填slug必填user_nameattachmentrecipientsuser_emailvisibilitysuppress_notificationsUpdate conversation
Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.
slug必填statussubjectassigneetag_listhold_untilCreate contact
Create a new contact (customer). Re:amaze REST: POST /contacts.
dataname必填email必填Update contact
Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.
id必填datanameemail已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
針對 Ably 的託管 MCP 伺服器，讓助理檢視頻道、線上狀態與用量統計、發布訊息，並查看應用程式設定。
io.usefulapi官方發布者
唯讀存取 ROLLER 場館資料：搜尋預訂、查詢產品可用性，並查看賓客、免責聲明、禮品卡與每日報表。
io.usefulapi官方發布者
託管的 Planerio 連接器，讓助理讀取排班、人力需求、可用人員、員工資料、缺勤與年假天數。
io.usefulapi官方發布者
唯讀存取 Marmin 的阿聯酋電子發票資料：發票、貸項通知單、UBL XML、Peppol 狀態與業務檔案。
io.usefulapi官方發布者
面向 Oyster 的遠端 MCP 伺服器，讓助理讀取團隊、休假、費用、合約與發票資料，並核准或拒絕相關申請。
{ "mcpServers": { "re-amaze": { "url": "https://re-amaze.usefulapi.io/mcp" } }}