LiveChat (Text) logo livechat.com

Live

LiveChat (Text) API and MCP server

LiveChat's API covers chats, tags and canned responses, but it takes a token or OAuth app and code you write and host. Sign in to LiveChat once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with LiveChat (Text).

LiveChat (Text) has no API for this. So we run one for you.

LiveChat (Text)'s own API, a GitHub MCP server and Cotlet compared
What you need LiveChat (Text)'s APIGitHub MCP serverCotlet
Use without an API key or code No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when LiveChat (Text) changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: Text Platform: MCP server · Text Platform: Agent Chat API · Text Platform: Configuration API · Zapier: LiveChat triggers and actions

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to LiveChat (Text) in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect LiveChat (Text) to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. LiveChat (Text) and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/livechat with its own method and path, such as POST /api/v1/livechat/chats/{chat_id}/messages, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the LiveChat (Text) API and MCP server do?

12 tools on your own LiveChat (Text) account. Agents call them as operations of the MCP tools livechat_read and livechat_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
LiveChat (Text) tools in Cotlet's MCP server and REST API
Tool What it does Access
list_chats Chats in My chats, Queued chats, Unassigned chats or Supervised chats, with customer, channel and last message. read
get_chat Full transcript of one chat with every message, private note and tag. read
list_archived_chats Archived chats, newest first, filtered by tag, agent, group, date or search text. read
list_tags Tags your role can see, with the group each one is limited to. read
list_canned_responses Shared and private canned responses with text, shortcuts, group and tags. read
list_agents Agents and groups a chat can be transferred to, with their current availability. read
send_message Reply to the customer in a chat, as you. writeasks first
send_private_note Add a message to a chat that only agents see. writeasks first
tag_chat Add tags to a chat, or remove them. write
transfer_chat Move a chat to another agent or to a group. writeasks first
archive_chat Stop an active chat and move it to Archives. writeasks first
save_canned_response Create a canned response, or change one by its ID. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All LiveChat (Text) use cases

Is it safe to connect LiveChat (Text)?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the LiveChat (Text) API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while LiveChat (Text) is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does LiveChat (Text) have an API?

LiveChat (Text) has a full REST API, the Agent Chat API and the Configuration API, but only a narrow official MCP server (checked 17 Oct 2026). The server at mcp.text.com documents 8 tools that all read: search, fetch, chat transcripts, archived chats, tickets and tags. It cannot reply, tag, transfer or change settings.

How do I get access?

Sign up free, open LiveChat (Text) under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to LiveChat (Text) yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so LiveChat (Text) sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: send_message, send_private_note, transfer_chat, archive_chat, save_canned_response wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agent work LiveChat tickets?

These tools cover chats, tags and canned responses. LiveChat's own ticketing is a legacy system that was retired from January 2025, depending on the plan, and accounts created after 1 June 2023 use HelpDesk for tickets. The official MCP lists ticket tools, but only to read.

Which LiveChat plan do I need?

Chats, tags and transfers work on every plan. Canned responses need Team, Business or Enterprise, and private notes on a transfer need Business or Enterprise. Tag creation is an admin task in Settings > Tags, so a normal agent account can use tags but not add them.

Should I use a LiveChat (Text) MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when LiveChat (Text) changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with LiveChat (Text)?

No. Cotlet is independent and not affiliated with LiveChat (Text).

Give your agent access to LiveChat (Text).

Free 7-day trial with 2,000 credits, no card needed.

Sign up free