Skip to content
Custom Connectors

Full read-write Claude connector for LiveChat

Let Claude reply, tag, and route conversations inside LiveChat

Stop switching tabs to triage the queue. Claude reads the active chat, drafts the reply in place, applies tags, transfers to the right agent, and adds an internal note for the next agent, with the customer-facing send held until you approve it.

LiveChat is a live chat and customer messaging platform where support teams handle real-time conversations, tickets, and canned responses across a website and app. Teams want Claude to do more than read transcripts: to reply in the active chat, tag and route conversations, and send once approved.

What is a LiveChat MCP server?

A LiveChat MCP server is a small hosted service that exposes LiveChat's data and actions to Claude over the Model Context Protocol, so Claude can tickets and customer conversations inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can LiveChat's current connector do today?

Today LiveChat ships an official connector through its Text platform MCP server, but it exposes a read-only tool set. Claude can search chats and read transcripts, yet replying to a customer, tagging, transferring, and adding internal notes are not available. A custom connector keeps that read coverage and adds scoped write actions with human-in-the-loop controls.

What does full read-write LiveChat access unlock?

Full read-write LiveChat access lets Claude post a message inside the active chat, keep the customer and channel intact, apply or remove tags, transfer to the right agent or group, and add internal notes for the next agent. The triage and drafting that used to mean switching tabs happen where the conversation already lives, with sends gated behind your approval.

  • Draft and send a message inside an active chat after you approve it
  • Apply or remove tags to triage and route incoming conversations
  • Transfer a chat to a specific agent or group
  • Add an internal note for the next agent without messaging the customer
  • Set your own routing status so chats reach the right available agents
  • Find every chat matching a query and propose batched responses

Can Claude reply inside an active LiveChat conversation?

Replying inside an active LiveChat conversation is what a full read-write connector enables: Claude drafts a message in the live chat, keeping the customer and channel intact. The draft is ready to review, and the actual send is a gated action that waits for your approval before anything reaches the customer.

Can Claude tag and route conversations in LiveChat?

Tagging and routing conversations in LiveChat is available through write tools that apply or remove tags and transfer a chat to a specific agent or group. Claude can also add an internal note for the next agent. You can let routine routing run on its own while customer-facing sends stay behind a confirmation step.

Can Claude add internal notes in LiveChat without messaging the customer?

Adding internal notes in LiveChat is a separate action from replying, so Claude can leave context for the next agent without messaging the customer. It can also search chats and propose batched responses. The connector inherits your agent permissions and never reaches data your account cannot see.

How a LiveChat connector works

We build a small MCP server that authenticates to LiveChat with OAuth 2.1 or a scoped Personal Access Token, using only the permissions the work needs. Read tools (search chats, read a transcript) and write tools (send message, tag, transfer, add internal note) are separated, and outbound or destructive actions like sending a customer message require your confirmation. Claude never has more access than the connected account, and we can add IP allowlisting where your setup calls for it.

Frequently asked questions

Can Claude reply inside a LiveChat conversation, or only read the transcript?
With a custom connector, Claude can draft and send a message inside the active chat, keeping the customer and channel intact. LiveChat's official Text platform connector is read-only, so it can search and summarize chats but cannot respond. In-chat replies need a purpose-built MCP server on the LiveChat API, with sending gated behind your approval.
Can Claude tag, transfer, or add internal notes in LiveChat?
Yes. A custom connector can expose write tools that apply or remove tags, transfer a chat to the right agent or group, and add an internal note for the next agent as you triage. These run as distinct actions you can choose to make automatic or hold behind a confirmation step, so routine routing moves fast while customer-facing sends stay under your control.
Does the connector get more access than my agent account has?
No. The connector authenticates through LiveChat's OAuth or a scoped Personal Access Token and inherits your existing agent permissions and group visibility. It never grants Claude more access to chats or customer data than you already have. Where your environment requires it, we can add IP allowlisting so the connector only reaches LiveChat from approved addresses.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.