Connect-MCP

Re:amaze MCP by usefulapi

io.usefulapi/re-amaze · v1.11.1

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

MCPremoteno credentialsMessagingCRM & sales

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 17 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 17 tools · 12 read, 5 write (incl. delete/pay) · Messaging, CRM & sales

Test call reamaze_list_conversations: needs a key: HTTP 401 (1,004 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://re-amaze.usefulapi.io/mcp

Tools

17 tools listed at last check
  • reamaze_list_conversations List/search conversations (support tickets). All filters optional; returns a page of conversations. Re:amaze REST: GET /conversations.
  • reamaze_get_conversation Get a single conversation by its slug. Re:amaze REST: GET /conversations/{slug}.
  • 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_contacts List/search contacts (customers). All filters optional; returns a page of contacts. Re:amaze REST: GET /contacts.
  • reamaze_get_contact Get a single contact (customer) by identifier (email or id). Re:amaze REST: GET /contacts/{identifier}.
  • reamaze_list_articles List/search help-center (knowledge-base) articles. All filters optional. Re:amaze REST: GET /articles.
  • reamaze_get_article Get a single help-center article by its slug. Re:amaze REST: GET /articles/{slug}.
  • reamaze_list_staff List staff (agent) accounts on the brand. Re:amaze REST: GET /staff.
  • reamaze_list_channels List channels (inboxes: email, chat, social, etc.). Channel slugs are used as `category` filters. Re:amaze REST: GET /channels.
  • reamaze_get_channel Get a single channel by its slug. Re:amaze REST: GET /channels/{slug}.
  • reamaze_report_volume Get the conversation-volume report (counts over time). Both dates optional. Re:amaze REST: GET /reports/volume.
  • 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_create_conversation Create a new conversation (support ticket) with its first message. Re:amaze REST: POST /conversations.
  • 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_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 Create a new contact (customer). Re:amaze REST: POST /contacts.
  • reamaze_update_contact Update fields on an existing contact. Only provided fields change. Re:amaze REST: PUT /contacts/{id}.

Badge

Connect-MCP badge for io.usefulapi/re-amaze

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/re-amaze.svg)](https://clawy.uk/mcp/s/io.usefulapi/re-amaze)