Manage Re:amaze conversations, messages, contacts and help articles. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"re-amaze": {
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"re-amaze": {
"type": "http",
"url": "https://re-amaze.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Re:amaze API token, Re:amaze login email and Re:amaze brand.
Create a token in Re:amaze → Settings → Developer → API Token. The brand is the subdomain in yourbrand.reamaze.io.
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: the login page asks for your Re:amaze API token, Re:amaze login email and Re:amaze brand. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Re:amaze connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
reamaze_list_conversations | read | List conversations List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations. |
reamaze_get_conversation | read | Get conversation Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}. |
reamaze_list_messages | read | 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 | read | List contacts List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts. |
reamaze_get_contact | read | Get contact Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}. |
reamaze_list_articles | read | List articles List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles. |
reamaze_get_article | read | Get article Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}. |
reamaze_list_staff | read | List staff List staff (agent) accounts on the brand. Re:amaze REST: GET /staff. |
reamaze_list_channels | read | List channels List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels. |
reamaze_get_channel | read | Get channel Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}. |
reamaze_report_volume | read | Report: volume Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume. |
reamaze_report_response_time | read | Report: response time Get the response-time report (how quickly conversations were answered). Both dates optional. Re:amaze REST: GET /reports/response_time. |
reamaze_create_conversation | write | Create conversation Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations. |
reamaze_reply_conversation | write | 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. |
reamaze_update_conversation | write | 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 | write | Create contact Create a new contact (customer). Re:amaze REST: POST /contacts. |
reamaze_update_contact | write | Update contact Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}. |
re_amaze_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
re_amaze_request_feature | Request a missing feature Tell usefulapi that the user needs something the Re:amaze tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
re_amaze_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Re:amaze tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
re_amaze_cancel_subscription | Cancel the Pro subscription Cancel the caller's Re:amaze Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run re_amaze_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Re:amaze server only. Subscribe with re_amaze_upgrade (it returns a Stripe Checkout link). Cancel any time with re_amaze_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running re_amaze_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Re:amaze. The server calls the Re:amaze API with your own Re:amaze access, so it sees only the data that your account can see.
The login page asks for your Re:amaze API token, Re:amaze login email and Re:amaze brand. See Before you connect for where to find them.
No. 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: the login page asks for your Re:amaze API token, Re:amaze login email and Re:amaze brand. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Re:amaze API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Re:amaze.
Yes, if you approve it. 5 of the 17 Re:amaze tools can create or change data. The other 12 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Re:amaze server only. Run re_amaze_usage_status to see how many calls you used.
Ask the AI to run re_amaze_upgrade: it returns a Stripe Checkout link. To cancel, run re_amaze_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with re_amaze_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.