Connect LiveChat to Claude Code

Let Claude reply, tag, and route conversations inside LiveChat. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect LiveChat to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect LiveChat, you add a LiveChat MCP server: a small hosted service that exposes LiveChat's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own LiveChat account. No API keys pasted into config files.

claude mcp add --transport http livechat https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in LiveChat once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same LiveChat access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the LiveChat API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when LiveChat changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build LiveChat connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same LiveChat connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own LiveChat account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on LiveChat's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to LiveChat?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the LiveChat account it signs in with. Revoking access is one click in LiveChat.

More on the LiveChat connector

LiveChat connector for claude.ai Gorgias + Claude Code Kustomer + Claude Code Zoho Desk + Claude Code

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.

Build my connector Talk to us