Re:amaze MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Re:amaze MCP by usefulapi is answering right now. Last checked 2 min ago. It exposes 17 tools. Last commit 10 Oct 2026.

Manage Re:amaze conversations, messages, contacts and help articles.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

99 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

1 Oct a tool changed version2 times that day

30 Sep a tool changed version

and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check Re:amaze MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add re-amaze --transport http https://re-amaze.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "re-amaze": {
      "url": "https://re-amaze.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.re-amaze]
url = "https://re-amaze.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "re-amaze": {
      "url": "https://re-amaze.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "re-amaze": {
      "url": "https://re-amaze.usefulapi.io/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

reamaze

reamaze_create_contact

Create a new contact (customer). Re:amaze REST: POST /contacts.

reamaze_create_conversation

Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.

reamaze_get_article

Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.

reamaze_get_channel

Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.

reamaze_get_contact

Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.

reamaze_get_conversation

Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.

reamaze_list_articles

List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.

reamaze_list_channels

List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.

reamaze_list_contacts

List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.

reamaze_list_conversations

List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.

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_staff

List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.

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_report_response_time

Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time.

reamaze_report_volume

Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.

reamaze_update_contact

Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.

reamaze_update_conversation

Update fields on an existing conversation (subject, status, tags, assignee). Only provided fields change. Re:amaze REST: PUT /conversations/{slug}.

Endpoints

URL	Transport	State	Latency	Checked
https://re-amaze.usefulapi.io/mcp	streamable-http	answering	77 ms	2 min ago

Alternatives to Re:amaze MCP by usefulapi

same job, measured the same way

Spruce Health MCP by usefulapi

by usefulapi

Read Spruce Health contacts, conversations, messages, phone lines and team members (read-only).

24 tools answering

Missive MCP by usefulapi

by usefulapi

Read email/chat conversations, messages, contacts and teams; draft, send and update threads.

19 tools answering

SimpleTexting MCP by usefulapi

by usefulapi

Send SMS/MMS, manage contacts, and read campaigns, messages and media on SimpleTexting.

11 tools answering

OpenPhone MCP by usefulapi

by usefulapi

Send and read OpenPhone messages, calls, contacts and phone numbers.

16 tools answering

Helpwise MCP by usefulapi

by usefulapi

Read Helpwise conversations, contacts, tags and reports; note, tag, assign, close; send one email.

21 tools answering

HelpCrunch MCP by usefulapi

by usefulapi

Manage HelpCrunch chats, customers, agents and knowledge-base articles.

12 tools answering

Groove MCP by usefulapi

by usefulapi

Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.

16 tools answering

Textline MCP by usefulapi

by usefulapi

Read Textline conversations, contacts and reports; send a text, add notes, resolve or transfer.

23 tools answering

Re:amaze MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Re:amaze MCP by usefulapi do?

It exposes 17 tools, read directly from the server on our last check. Among them: reamaze_create_contact, reamaze_create_conversation, reamaze_get_article, reamaze_get_channel, reamaze_get_contact, reamaze_get_conversation and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Re:amaze MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 99 ms. The bar chart above shows every period we have measured.

How do I connect Re:amaze MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Re:amaze MCP by usefulapi need an API key?

No. Re:amaze MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Re:amaze MCP by usefulapi?

It answers our handshake in 99 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Re:amaze MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.