io.usefulapi/re-amaze
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Re:amaze MCP by usefulapi
Publisher-provided description
Manage Re:amaze conversations, messages, contacts and help articles.
Summary by lookupd
Lets agents list, create and update support conversations, contacts and channels, reply to customers, and pull help articles and reports.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http re-amaze https://re-amaze.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add re-amaze --url https://re-amaze.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"re-amaze": {
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (17 tools)
Publisher-provided text
reamaze_list_conversationsList/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.reamaze_get_conversationGet a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.reamaze_list_messagesList messages. If `conversation` (a slug) is given, list that conversation's messages (GET /conversations/{slug}/messages); otherwise list messages across the breamaze_list_contactsList/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.reamaze_get_contactGet a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.reamaze_list_articlesList/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.reamaze_get_articleGet a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.reamaze_list_staffList staff (agent) accounts on the brand. Re:amaze REST: GET /staff.reamaze_list_channelsList channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.reamaze_get_channelGet a single channel by its slug. Re:amaze REST: GET /channels/{slug}.reamaze_report_volumeGet the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.reamaze_report_response_timeGet the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.reamaze_create_conversationCreate a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.reamaze_reply_conversationAdd a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.reamaze_update_conversationUpdate fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.reamaze_create_contactCreate a new contact (customer). Re:amaze REST: POST /contacts.reamaze_update_contactUpdate fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.
Details
- Version: 1.37.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 550 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/re-amaze/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/re-amaze)
- 62092 servers
- Last crawl: 2026-11-11T17:17:22.074Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp