Replyze/replyze-mcp

The Replyze MCP server lets an AI assistant work with your customer support: find and read conversations, reply to customers, leave internal notes for your team, assign conversations, look up contacts and search the knowledge base your support AI answers from. It is a remote server: you give your assistant a URL and an API key. There is nothing to install or run. Replyze is AI customer support: an AI agent that answers from your docs, live chat for your website, and one inbox for chat, email, WhatsApp and Telegram.
Create a free account · Live demo · Docs
## Quickstart
1. Make an API key. Create a free account, open Settings → Integrations → Developer and create a key. For a first try, tick only the read scopes (conversations:read, contacts:read, knowledge:read): the assistant can look everything up but can't write to a customer.
2. Add the server to your assistant. In Claude Code:
bash
claude mcp add --transport http replyze https://client.replyze.chat/api/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
Claude Desktop, Cursor, VS Code and other clients are below.
3. Ask it something, for example "Which open conversations are waiting on us? Group them by topic."
| Server | URL | Sign-in |
| Your workspace | https://client.replyze.chat/api/mcp | API key as a Bearer token |
| Your public help center | https://client.replyze.chat/api/mcp/kb/ | none |
## Contents
Quickstart ·
What you can ask ·
Example ·
Tools ·
Set up (Claude Code · Claude Desktop · Cursor · VS Code · Other clients · claude.ai and ChatGPT) ·
Public help center ·
Permissions and safety ·
Protocol ·
Errors
## What you can ask
"Which open conversations are waiting on us? Group them by topic."
"Find everything Maria Lopez wrote to us this month and summarize it before my call."
"Draft replies for the open refund questions from our knowledge base. Don't send anything."
"Assign the conversations about invoices to Ana and leave her a note with the context."
"What do customers ask that our knowledge base doesn't answer?"
"Is our return window 30 or 60 days? Check the knowledge base."
## Example
An example of how a session goes (the assistant decides which tools to call):
> You: Which open conversations mention a refund? Draft a reply for each, but don't send them.
> The assistant calls search_conversations(query="refund", status="open"), then get_conversation for each result and search_knowledge(query="refund policy"), and writes the drafts in the chat.
> You: The draft for #4812 is good. Send it, and leave a note for the team that we promised a refund within 5 days.
> The assistant calls send_message(conversation_id=4812, content="..."), so the customer gets the reply on the channel they wrote from, then add_note(conversation_id=4812, content="..."), which only the team sees.
## Tools
What a key can do depends on its scopes. tools/list shows only the tools the key can use, and a write scope includes the read scope of the same resource (conversations:write can also read conversations).
| Tool | Scope | What it does | Arguments |
| search_conversations | conversations:read | Finds conversations, newest activity first. Matches the contact's name, email or phone, the subject, and anything the visitor or the team wrote (not internal notes). | query, status (open, pending, snoozed, resolved, closed, spam), contact_id, assigned_agent_id, limit (1 to 50, default 10); all optional |