Re:amaze MCP server

What the model can do

Re:amaze help desk: conversations by status, channel, tag and date with their customer and assignee; one conversation with its staff replies and internal notes (what customers wrote is not returned); contacts by name or email; FAQ articles; satisfaction ratings; daily volume and response-time reports; channels, staff and response templates. When you ask, can add an internal note, reply to the customer, open a conversation for a customer, change status, tags or assignee, create or rename contacts and manage their notes, write or edit FAQ articles, and post a status page incident.

Reads

• reamaze_list_conversationsRe:amaze conversations, 30 a page: subject, status, channel, tags, customer name and email, assignee, when created and when the customer last wrote.
• reamaze_get_conversationOne Re:amaze conversation by slug: subject, status, channel, tags, customer, assignee, and its latest 30 messages (newest first) with who sent each…
• reamaze_list_contactsRe:amaze contacts (account-wide), 30 a page: name, friendly name and email.
• reamaze_list_articlesRe:amaze FAQ articles, 30 a page: title, slug, status (published, draft or internal), topic, URL, author name, when updated…
• reamaze_satisfaction_ratingsRe:amaze satisfaction ratings (1 to 5), 30 a page, newest first, across every brand unless this_brand_only: rating, conversation id, assignee id…
• reamaze_reportRe:amaze reports for a window of 1 day to 1 year (default the last 30 days)…
• reamaze_list_channelsThis Re:amaze brand's channels (name, slug, type such as email, chat or sms, the channel's own address…
• reamaze_list_response_templatesRe:amaze response templates (saved replies), including the user's personal ones: id, name, group and text.

Acts, when you ask

These change something in Re:amaze. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• reamaze_add_noteAdds an internal note to a Re:amaze conversation, as the token's user.
• reamaze_replySends a reply to the customer in a Re:amaze conversation, through its channel (email, chat, SMS or social), as the token's user…
• reamaze_create_conversationOpens a new Re:amaze conversation in a channel on behalf of a customer (name and email), with a first message from them.
• reamaze_update_conversationChanges a Re:amaze conversation's status (open, responded, done, spam, archived or on_hold until a time), replaces its tags with the list given…
• reamaze_create_contactCreates a Re:amaze contact (account-wide) with a name and an email or an E.164 mobile number.
• reamaze_update_contactRenames a Re:amaze contact (name or friendly name), found by email or E.164 mobile; the identifier itself cannot change.
• reamaze_add_contact_noteAdds a note to a Re:amaze contact, found by email or E.164 mobile, as the token's user.
• reamaze_update_contact_noteReplaces the text of one note on a Re:amaze contact.
• reamaze_delete_contact_notePermanently deletes one note from a Re:amaze contact.
• reamaze_create_articleWrites a Re:amaze FAQ article.
• reamaze_update_articleChanges a Re:amaze FAQ article's title or body.
• reamaze_create_incidentPosts an incident on the brand's public Re:amaze status page with its first update (investigating, identified, monitoring or resolved)…

Connect it

First connect Re:amaze on Dashboard → Connections, then add Memtro to your client once. The Re:amaze tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Re:amaze connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which conversations are still open from yesterday?
• › What was our response time over the last 30 days?
• › Which FAQ articles are still drafts?
• › Which recent satisfaction ratings were 1 or 2?
• › Is there a saved reply for refund requests?

Questions

Is this an official Re:amaze MCP server?

No. It is Memtro's MCP server with Memtro's Re:amaze connector behind it: the connector reads Re:amaze through its API with the credentials you connect on Dashboard → Connections, and Re:amaze publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Re:amaze?

Only when you ask, and only what it has been granted: add an internal note to a conversation (staff only); reply to the customer in a conversation (sent through its channel); open a conversation on a customer's behalf; change a conversation's status, tags or assignee; create a contact; rename a contact; add a note to a contact; edit a contact's note; delete a contact's note; write an FAQ article as a draft, internal or published; edit an FAQ article's title or body; post an incident on the public status page. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server