usefulapi

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

Claude

Open Settings → Connectors → Add custom connector
Paste this URL:
https://re-amaze.usefulapi.io/mcp
Authenticate with Re:amaze when prompted

Cursor · VS Code · Windsurf · Cline

Add to your MCP config, then reload & authorize:

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

live17 toolsFree 100 tool calls / monthPro $9/mo · $90/yr

Tools 17

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

Pricing

Plan	Price	Limit
Free	$0	100 tool calls / month
Pro	$9/mo · $90/yr	Unlimited

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.