re-amaze

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.usefulapi/re-amaze and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 29 Sept 2026. Not supplied by the maker.

• 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

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.