Re:amaze MCP by usefulapi

io.usefulapi/re-amaze

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

Yes, your AI can use this right now.Answered a live MCP handshake in 141 ms with no sign-in needed and exposes 17 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://re-amaze.usefulapi.io/mcp

17 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
reamaze_list_conversationsread-only

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

reamaze_get_conversationread-only

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

reamaze_list_messagesread-only

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_contactsread-only

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

reamaze_get_contactread-only

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

reamaze_list_articlesread-only

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

reamaze_get_articleread-only

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

reamaze_list_staffread-only

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

reamaze_list_channelsread-only

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

reamaze_get_channelread-only

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

reamaze_report_volumeread-only

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

reamaze_report_response_timeread-only

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

reamaze_create_conversationcan modify

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

reamaze_reply_conversationcan modify

Add a message to an existing conversation — a customer-facing reply or an internal note. Re:amaze REST: POST /conversations/{slug}/messages.

reamaze_update_conversationcan modify

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

reamaze_create_contactcan modify

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

reamaze_update_contactcan modify

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

Alternatives in Email & Messaging

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”