Re:amaze MCP by usefulapi

Last 30 days

Uptime

100%

Response time

283 ms typical, 283 ms slowest 5%

Last check

5 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

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

17 tools

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

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks