LiveChat MCP server

What the model can do

LiveChat (Text): current chats, archived chats searched by words, date, group or customer email, a chat's transcript, agents, groups and tags. Can add an internal note that only agents see, reply to the customer, tag or untag a thread, transfer, close, start or resume a chat, add an agent to a chat, and ban a customer.

Reads

• livechat_list_chatsLiveChat chats (current and recent), newest first: chat and latest thread id, whether active, who is in it and the last message.
• livechat_search_archivesSearch LiveChat's archive of chat threads by words, date range, group, agent or customer email, newest first: one row per thread with its chat id…
• livechat_get_chatOne LiveChat chat thread with its transcript: messages and system events oldest first (text trimmed, internal notes marked), the people in it…
• livechat_list_agentsLiveChat agents: id (their email), name, role, whether accepting chats, and their groups.
• livechat_list_groupsLiveChat groups (where chats are routed): id, name, language and routing status.
• livechat_list_tagsThe tags defined in LiveChat for some groups (General, group 0, by default), with which groups each applies to.

Acts, when you ask

These change something in LiveChat. 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.

• livechat_add_internal_noteAdds an internal note to a LiveChat chat, visible to agents only and never to the customer.
• livechat_tag_threadTags a LiveChat chat thread with an existing tag (case sensitive, from livechat_list_tags).
• livechat_send_messageSends a message in a LiveChat chat that the customer sees (visibility all), posted as the token's own agent, who must already be in the chat.
• livechat_transfer_chatTransfers an active LiveChat chat to a group or to named agents, who receive it.
• livechat_close_chatCloses (deactivates) a LiveChat chat: its open thread ends and no more messages can be sent to it; the customer sees the chat end.
• livechat_start_chatStarts a new LiveChat chat as the token's agent, optionally with an existing customer and up to 4 other agents, in given groups.
• livechat_resume_chatReopens an archived LiveChat chat, starting a new thread in it.
• livechat_untag_threadRemoves a tag (case sensitive) from a LiveChat chat thread.
• livechat_add_agent_to_chatAdds an agent to an active LiveChat chat; the agent sees the chat.
• livechat_ban_customerBans a LiveChat customer for a number of days: all their active sessions are disconnected at once and no new chats are accepted from them until the…

Connect it

First connect LiveChat on Dashboard → Connections, then add Memtro to your client once. The LiveChat 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 LiveChat 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

• › What did visitors ask about pricing on chat last week?
• › Show me the transcript of Dan Fletcher's last chat
• › Which chats in the Sales group are active right now?
• › Tag the Northwind chat thread as Refund
• › Reply in the Acme chat that the order ships tomorrow, then transfer it to Billing

Questions

Is this an official LiveChat MCP server?

No. It is Memtro's MCP server with Memtro's LiveChat connector behind it: the connector reads LiveChat through its API with the credentials you connect on Dashboard → Connections, and LiveChat 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 LiveChat?

Only when you ask, and only what it has been granted: add an internal note to a chat, visible to agents only; tag a chat thread with an existing tag; reply to the customer in a chat, which they see; transfer a chat to agents or a group; close (deactivate) a chat; start a chat, optionally with a first message the customer sees; resume an archived chat; remove a tag from a chat thread; add an agent to a chat; ban a customer from chatting for a number of days. 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