Re:amaze MCP by usefulapi
Manage Re:amaze conversations, messages, contacts and help articles
Reviews
No review yet. Used Re:amaze MCP by usefulapi? Be the first to help others choose.What it does
Re:amaze MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 4h ago (live check)Hosted endpoint
https://re-amaze.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http re-amaze https://re-amaze.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"re-amaze": {
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 4h agoONLINE Re:amaze MCP by usefulapi answered an MCP connection on 16 Nov 2026 and introduced itself as re-amaze-mcp 1.39.3 (MCP protocol 2025-06-18).
17 tools offered to AI assistants
reamaze_list_conversations· List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.reamaze_get_conversation· Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.reamaze_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.reamaze_list_contacts· List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.reamaze_get_contact· Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.reamaze_list_articles· List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.reamaze_get_article· Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.reamaze_list_staff· List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.reamaze_list_channels· List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.reamaze_get_channel· Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.reamaze_report_volume· Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.reamaze_report_response_time· Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.
Show 5 more
reamaze_create_conversation· Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.reamaze_reply_conversation· Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.reamaze_update_conversation· Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.reamaze_create_contact· Create a new contact (customer). Re:amaze REST: POST /contacts.reamaze_update_contact· Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.40.0 | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Hosted endpoint | https://re-amaze.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Website | https://usefulapi.io/re-amaze/ | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 27m ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 27m ago |
Change history
- VERSION16 Nov 20261.39.3 → 1.40.0
- VERSION16 Nov 20261.39.2 → 1.39.3
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.3 → 1.37.0
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
- VERSION28 Oct 20261.26.0 → 1.27.0
- VERSION28 Oct 20261.25.0 → 1.26.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Re:amaze MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Re:amaze MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Re:amaze MCP by usefulapi
How do I connect Re:amaze MCP by usefulapi?
Use the hosted endpoint https://re-amaze.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Re:amaze MCP by usefulapi offer?
When Electra Index connected on 16 Nov 2026, it listed 17 tools: reamaze_list_conversations, reamaze_get_conversation, reamaze_list_messages, reamaze_list_contacts, reamaze_get_contact, reamaze_list_articles, reamaze_get_article, reamaze_list_staff and more. The full list is in "Live check" above.
Is Re:amaze MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 4h ago.