Re:amaze MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026

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

The publisher's own server: Ably MCP by usefulapi

Overview

AI-generated overview

Hosted MCP server that lets an assistant read and manage Re:amaze support conversations, messages, contacts, help articles and reports.

What you can do
  • List, search and read conversations (tickets) and their messages
  • Look up contacts (customers) and staff accounts
  • Browse channels (inboxes) and help-center articles
  • Pull conversation-volume and response-time reports
  • Create conversations, reply with customer-facing messages or internal notes, and update conversation fields
  • Create and update contacts
When to use it
Useful when a support or success team works in Re:amaze and wants an assistant to triage tickets, look up a customer's conversations, draft replies, or check volume and response-time trends without switching apps.
Requirements
Remote endpoint only, no local install. Connect with the server URL; the server signs you in with OAuth and the login page asks for your Re:amaze credentials, which are stored per user. No API key or Authorization header in the client config. A free plan allows 50 tool calls per month; paid plans raise the limit.
Before you install
Several tools write to Re:amaze: creating conversations and contacts, replying to conversations (including customer-facing messages) and updating conversation or contact fields. The server asks for Re:amaze credentials at login, and usage is metered; paid plans are billed through a checkout link, and plan changes charge the price difference immediately with no refund for the current period.

Installation

In SourceWeft

  1. Open Re:amaze MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fre-amaze/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "re-amaze-by-usefulapi": {
      "type": "http",
      "url": "https://re-amaze.usefulapi.io/mcp"
    }
  }
}

README

Re:amaze MCP by usefulapi

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

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://re-amaze.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http re-amaze https://re-amaze.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "re-amaze": {      "url": "https://re-amaze.usefulapi.io/mcp"    }  }}

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.

Tools

ToolTypeWhat it does
reamaze_list_conversationsreadList conversations
reamaze_get_conversationreadGet conversation
reamaze_list_messagesreadList messages
reamaze_list_contactsreadList contacts
reamaze_get_contactreadGet contact
reamaze_list_articlesreadList articles
reamaze_get_articlereadGet article
reamaze_list_staffreadList staff
reamaze_list_channelsreadList channels
reamaze_get_channelreadGet channel
reamaze_report_volumereadReport: volume
reamaze_report_response_timereadReport: response time
reamaze_create_conversationwriteCreate conversation
reamaze_reply_conversationwriteReply to conversation
reamaze_update_conversationwriteUpdate conversation
reamaze_create_contactwriteCreate contact
reamaze_update_contactwriteUpdate contact
re_amaze_usage_statusmetaUsage status (free-tier meter)
re_amaze_request_featuremetaRequest a missing feature
re_amaze_upgrademetaUpgrade to Pro or Pro+
re_amaze_cancel_subscriptionmetaCancel the Pro subscription

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.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+$39/mo or $390/yr (2 months free)100,000 tool calls / month

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].

License

MIT

Source: servers/re-amaze/README.md at commit f22f848

Tools

17

reamaze_list_conversations

List conversations

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

Parametersfortagpagesortfilterfor_idorigincategoryend_datestart_date

reamaze_get_conversation

Get conversation

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

Parametersslugrequired

reamaze_list_messages

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.

Parameterstagpagefilteroriginincludesent_bycategoryend_datestart_dateconversation

reamaze_list_contacts

List contacts

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

Parameterspagefilter

reamaze_get_contact

Get contact

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

Parametersidentifierrequired

reamaze_list_articles

List articles

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

Parameterspagefilter

reamaze_get_article

Get article

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

Parametersslugrequired

reamaze_list_staff

List staff

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

Parameterspage

reamaze_list_channels

List channels

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

Parameterspage

reamaze_get_channel

Get channel

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

Parametersslugrequired

reamaze_report_volume

Report: volume

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

Parametersend_datestart_date

reamaze_report_response_time

Report: response time

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

Parametersend_datestart_date

reamaze_create_conversation

Create conversation

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

Parametersstatussubjectrequiredassigneecategoryrequiredtag_listuser_namerequiredrecipientsuser_emailrequiredmessage_bodyrequired

reamaze_reply_conversation

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.

Parametersbodyrequiredslugrequireduser_nameattachmentrecipientsuser_emailvisibilitysuppress_notifications

reamaze_update_conversation

Update conversation

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

Parametersslugrequiredstatussubjectassigneetag_listhold_until

reamaze_create_contact

Create contact

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

Parametersdatanamerequiredemailrequired

reamaze_update_contact

Update contact

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

Parametersidrequireddatanameemail

Version history

25
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.3Nov 7, 2026
  6. v1.35.3Nov 5, 2026
  7. v1.35.2Nov 5, 2026
  8. v1.35.1Nov 4, 2026
  9. v1.35.0Nov 3, 2026
  10. v1.34.1Nov 3, 2026
  11. v1.33.0Nov 1, 2026
  12. v1.31.0Oct 31, 2026
  13. v1.30.0Oct 31, 2026
  14. v1.29.2Oct 30, 2026
  15. v1.29.0Oct 30, 2026
  16. v1.24.0Oct 26, 2026
  17. v1.21.3Oct 25, 2026
  18. v1.21.0Oct 25, 2026
  19. v1.20.0Oct 24, 2026
  20. v1.17.0Oct 23, 2026
  21. v1.16.4Oct 22, 2026
  22. v1.16.3Oct 21, 2026
  23. v1.11.1Oct 9, 2026
  24. v1.10.0Oct 9, 2026
  25. v1.0.0Sep 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations