Disclaimer: This project is not affiliated with, endorsed by, or officially connected to Reamaze in any way. I built this because I thought it would be useful for integrating Reamaze with AI-powered workflows, and figured others might find it handy too.
An MCP (Model Context Protocol) server that connects Claude Code to the Reamaze customer support platform. Provides tools for listing/reading conversations, replying to tickets, searching contacts, managing notes, and browsing response templates.
- Node.js 18+
- A Reamaze account with API access
- Claude Code CLI
git clone https://github.com/kennymkchan/reamaze-mcp-server.git
cd reamaze-mcp-server
npm install
npm run build- Brand: Your Reamaze subdomain (e.g. if your dashboard is
acme.reamaze.com, the brand isacme) - Email: The email address of a staff user with API access
- API Token: Found in Reamaze under Settings > API > API Token
Run the following command, replacing the placeholder values with your actual credentials:
claude mcp add reamaze \
-e REAMAZE_BRAND=yourbrand \
-e REAMAZE_EMAIL=you@example.com \
-e REAMAZE_API_TOKEN=your_api_token_here \
-- node /absolute/path/to/reamaze-mcp-server/build/index.jsThis stores the server config (including env vars) in ~/.claude.json. Credentials are never committed to the repo.
If you run a Shopify store, you can pair this server with the Shopify MCP server to give Claude full context when replying to customer emails. A typical workflow looks like:
- List open Reamaze tickets to see what needs attention
- Read a customer's conversation thread
- Look up their order in Shopify (by order number, email, etc.) to check fulfillment status, tracking info, or payment details
- Draft a reply with accurate, order-specific information
- Send the reply after you approve it
This turns Claude Code into an AI-assisted support agent that can cross-reference real order data before responding -- no copy-pasting between tabs.
- Triage and tagging -- Scan incoming tickets, update statuses, and apply tags to keep your queue organized
- Canned response lookup -- Search your Reamaze templates to find the right starting point for a reply
- Internal notes -- Add staff-only notes to contacts or conversations for context that customers don't see
- Bulk operations -- Work through a backlog of tickets in a single session, archiving resolved conversations as you go
| Tool | Description |
|---|---|
list_conversations |
List tickets with optional filter (open, unassigned, archived, all) and pagination |
get_conversation_count |
Quick count of conversations by filter without fetching full ticket data |
get_conversation |
Get a full conversation thread with all messages |
reply_to_conversation |
Send a reply or internal note to a conversation |
search_contacts |
Search contacts by name or email |
get_contact |
Get detailed contact info including notes |
list_response_templates |
List canned response templates, optionally filtered by keyword |
add_note |
Add an internal staff note to a contact |
# Build
npm run build
# Rebuild after changes
npm run build
# Run directly (requires env vars to be set)
REAMAZE_BRAND=yourbrand REAMAZE_EMAIL=you@example.com REAMAZE_API_TOKEN=yourtoken npm startsrc/
index.ts # MCP server setup and tool definitions
reamaze-client.ts # Reamaze REST API client
types.ts # TypeScript interfaces and constants