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