Get the FREE Ultimate OpenClaw Setup Guide →

reamaze

MCP server from kennymkchan/reamaze-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio kennymkchan-reamaze-mcp-server node /absolute/path/to/reamaze-mcp-server/build/index.js \
  --env REAMAZE_BRAND="Your Reamaze subdomain brand (e.g. yourbrand)" \
  --env REAMAZE_EMAIL="Staff user email with API access" \
  --env REAMAZE_API_TOKEN="Your Reamaze API token"

How to use

This MCP server provides a bridge between Claude Code and your Reamaze customer support workspace. It exposes tools to list and read conversations, reply to tickets (including internal notes), search contacts, manage notes, and browse response templates. By registering the MCP with Claude Code and supplying your Reamaze credentials, Claude can fetch contextual conversation data and perform actions in Reamaze as part of AI-assisted workflows. The available tools enable building end-to-end support flows such as listing open tickets, reading a thread, looking up customers, drafting replies, and applying canned responses or internal notes, all within Claude Code’s interface.

To use it, install and run the MCP server locally, then register it with Claude Code using your Reamaze credentials. After registration, Claude will be able to invoke the tools by name (e.g., list_conversations, get_conversation, reply_to_conversation, search_contacts, get_contact, list_response_templates, add_note) and pass necessary parameters. You can combine these tools to create automated or semi-automated workflows—for example, pulling a customer’s conversation, cross-referencing their contact details, and drafting a reply with templated content before sending.

How to install

Prerequisites:\n- Node.js 18+ (install from https://nodejs.org/)\n- A Reamaze account with API access (brand, email, API token)\n- Claude Code CLI (for MCP registration)\n\nSetup steps:\n1. Clone the repository and build the server:\nbash\ngit clone https://github.com/kennymkchan/reamaze-mcp-server.git\ncd reamaze-mcp-server\nnpm install\nnpm run build\n\n2. Obtain your Reamaze API credentials:\n- Brand: your Reamaze subdomain brand (e.g. acme)\n- Email: staff user email with API access\n- API Token: generated in Reamaze Settings > API > API Token\n3. Register the MCP server with Claude Code:\nbash\nclaude mcp add reamaze \\n -e REAMAZE_BRAND=yourbrand \\n -e REAMAZE_EMAIL=you@example.com \\n -e REAMAZE_API_TOKEN=your_api_token_here \\n -- node /absolute/path/to/reamaze-mcp-server/build/index.js\n\nThis stores the server config (including env vars) in ~/.claude.json. Credentials are not committed to the repo.\n4. Run the server locally (during development):\nbash\nREAMAZE_BRAND=yourbrand REAMAZE_EMAIL=you@example.com REAMAZE_API_TOKEN=yourtoken npm start\n\n

Additional notes

Tips and notes:\n- Keep your Reamaze API token secure; the credentials are stored in Claude Code’s config file, not in the repository.\n- The build step compiles TypeScript sources to build/index.js, which is what the MCP server runs. Ensure the build step completes successfully before starting or registering with Claude Code.\n- When registering, the example uses a placeholder absolute path to the built index.js; replace with the actual path on your system.\n- If you rotate API credentials, update the environment variables and re-register if needed.\n- The MCP exposes tools like list_conversations, get_conversation, reply_to_conversation, search_contacts, and more; refer to the project’s Tool definitions for required payload formats.\n- Environment variables can be set per-run or as part of the command line when starting the server.\n- If you encounter network or API permission errors, verify the Reamaze account has API access and that the brand/subdomain is correct.

Related MCP Servers

Sponsor this space

Reach thousands of developers