100+ integrations are ready to connect to your AI.Connect your first MCP

Re:amaze MCP server for your AI

Read a whole conversation, reply or leave an internal note, assign and tag work, look a customer up, keep help articles current, and post status page updates in your live Re:amaze brand.

PopMCPRe:amaze

Which open conversations have no one assigned, and what is each customer asking

Supported Re:amaze tools

Every call in Re:amaze's API reference, from conversations and contacts to reports and status page incidents, plus the events the server can watch.

46 tools in the full catalog: 29 read and 17 write. 36 load by default, and the rest are found with tool search.

reamaze_create_article

Create a help article with no topic.

reamaze_create_contact

Create a contact with an email or a mobile number.

reamaze_create_incident

Post a new incident on this brand's public status page, where customers can read it, so confirm the wording first.

reamaze_get_article

Read one help article in full: title, body, status, link, dates, author and topic.

reamaze_get_contact_overview

Everything about one person at a glance: their contact record, staff notes, other emails and handles, and latest 10 conversations.

reamaze_get_incident

Read one status page incident: title, status, dates, updates and the systems affected, with the ids reamaze_update_incident needs.

reamaze_get_response_time_report

How fast staff respond, in seconds, for this brand.

reamaze_get_staff_report

Each staff member's numbers for this brand, keyed by name: responses, response time in seconds, appreciations and responses by date.

reamaze_get_support_summary

This brand's support numbers for a date range in one call: conversation volume, response times in seconds, each staff member's numbers, tag counts and each channel's numbers.

reamaze_get_tag_report

How often each tag was used for this brand.

reamaze_get_volume_report

How many conversations came in each day for this brand.

reamaze_list_articles

Search or list this brand's help articles, 30 to a page.

reamaze_list_contacts

Search or list contacts, 30 to a page.

reamaze_list_incidents

List this brand's status page incidents.

reamaze_list_systems

List the systems on this brand's status page.

reamaze_update_article

Change a help article's title, body or status.

reamaze_update_contact

Change a contact's name, friendly name, avatar or customer data, or add notes.

reamaze_update_incident

Add an update to a status page incident, change its title, or change how its systems are affected.

reamaze_create_conversation

Start a new conversation on behalf of a customer, as a support form would.

reamaze_get_conversation

Read one conversation: subject, status, tags, author, assignee, channel, custom data, followers and the last staff and customer messages.

reamaze_get_conversation_thread

Read a whole conversation in one call: its details, then its messages oldest first, including internal notes (visibilityName internal).

reamaze_list_conversations

List conversations in this brand, 30 to a page, newest first.

reamaze_update_conversation

Change a conversation: status, assignee, tags, custom data, or the channel it sits in.

reamaze_create_contact_note

Add a staff note to a contact.

reamaze_create_response_template

Create a saved reply for the team, or a personal one.

reamaze_list_contact_notes

List all staff notes on one contact.

reamaze_list_response_templates

Search or list saved replies, including the personal ones this person may see.

reamaze_update_response_template

Change a saved reply's name, body or whether it is personal.

reamaze_create_conversation_message

Add to a conversation: a reply the customer receives (visibility regular) or a note only staff see (visibility internal).

reamaze_list_conversation_messages

List the messages of one conversation, 30 to a page, newest first.

reamaze_list_messages

List messages across all conversations in this brand, 30 to a page, newest first.

reamaze_create_staff

Add a staff user to the Re:amaze account.

reamaze_list_channels

List this brand's channels: email, chat, social, SMS, voice and more.

reamaze_list_staff

List the staff of the whole Re:amaze account, oldest first.

reamaze_get_brand_overview

A map of this Re:amaze brand: its channels with slugs, staff with emails, active status page incidents and systems with ids.

reamaze_list_satisfaction_ratings

List customer satisfaction ratings for this brand, 30 to a page, newest first.

reamaze_create_contact_identity

Attach another email, phone number or social handle to a contact.

reamaze_create_topic_article

Create a help article in a topic.

reamaze_get_channel_summary_report

Each channel's numbers for this brand: staff and customer responses, average response time in seconds, appreciations, active, resolved and archived conversations, average satisfaction and thread size.

reamaze_list_active_incidents

List this brand's status page incidents that are still active.

reamaze_list_contact_identities

List every email, phone number and social handle attached to one contact.

reamaze_list_topic_articles

List the help articles in one topic, 30 to a page.

reamaze_delete_contact_note

Delete a staff note from a contact.

reamaze_get_response_template

Read one saved reply: name, body and group.

reamaze_update_contact_note

Change a staff note on a contact.

reamaze_get_channel

Read one channel: name, email, type, visibility, verification, spam filter, signature and brand.

Connect Re:amaze to Claude, ChatGPT and Claude Code

Credentials off one Re:amaze screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

Paste your brand address, the email you sign in with, and your API token from Settings, Developer, API Token. Authentication runs server-side over HTTPS, and the connection is locked to one Re:amaze brand.

Brand addressacme.reamaze.io
Login emailyou@example.com
API token••••••••••••3f7a
ConnectionVerified

Then just ask for the work

  • “Which open conversations have no one assigned, and what is each customer asking”

    • list_conversations
    • get_conversation_thread
  • “Summarize this conversation, leave an internal note, and assign it to Jean”

    • get_conversation_thread
    • create_conversation_message
    • list_staff
    • update_conversation
  • “Show everything we know about bob@example.com and his latest conversations”

    • get_contact_overview
    • list_contact_notes
  • “How did support do last month: volume, response times and the busiest tags”

    • get_support_summary
    • list_satisfaction_ratings
  • “Post a status page incident for checkout, then mark it resolved once it is fixed”

    • list_systems
    • create_incident
    • update_incident

Use Re:amaze from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

Register PopMCP as a custom connector, then let ChatGPT read and update the account.

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Re:amaze MCP server questions

What teams ask before putting Re:amaze behind an AI client.

What do I paste in to connect Re:amaze?

Three things: your brand address, such as acme.reamaze.io, the email you sign in with, and your API token. The token is under Settings, Developer, API Token, where you can select Generate New Token if there isn't one yet. Re:amaze says API access comes with every account, and there is no OAuth redirect or app to set up.

How many Re:amaze operations does the server expose?

All 42 operations in Re:amaze's API reference, 25 reads and 17 writes, plus 4 tools that combine several calls. 32 of the operations and those 4 tools load into your AI client by default, and the rest stay searchable. Nothing documented is left out. The reference has no routes for webhooks, or for listing topics, brands or tags, so those are not available.

Can the agent send a message to a customer?

Yes, so it has to choose each time. create_conversation_message has no default: visibility regular sends a reply the customer receives, and visibility internal adds a note only staff see. The AI is told to confirm before a regular reply. A read-only connection in PopMCP hides every write tool.

My Re:amaze account has several brands. How does that work?

One connection covers one brand, because Re:amaze picks the brand from the address each request goes to. Conversations, messages, channels, articles, saved replies and the status page all stay on that brand, and reports and ratings are held to it too. Connect each brand separately to reach it. Contacts and staff belong to the whole account in Re:amaze, so those tools show all of them.

Whose name do changes appear under?

Each Re:amaze user has their own token, and it acts as them. Replies and notes are recorded as that person unless a tool names another sender, and their role decides what is allowed. Reports and satisfaction ratings need the access_reports permission. A refused tool says what is missing.

Which Re:amaze events can PopMCP watch?

New messages, customers writing in, conversations added or changed, satisfaction ratings received or changed, and changes to contacts, help articles, saved replies, channels, teammates, incidents and system status. PopMCP checks for these by reading your lists, because Re:amaze's API reference has no webhook routes.

Do I have to run or host the Re:amaze MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

How do I connect Re:amaze to Claude Code?

Connect Re:amaze in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Re:amaze on the consent screen. The Re:amaze tools are then available in that session, and no Re:amaze credential is stored on your machine.

Why do only 36 of the 46 tools load by default?

Loading 46 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 36-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

What is the difference between a tool and a trigger?

A tool is something your AI calls, and there are 46 here. A trigger is something PopMCP watches for you: 12 Re:amaze events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Re:amaze.

Connect Re:amaze to your AI in minutes

Launch a hosted MCP endpoint for Re:amaze, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP