JivoChat logo jivochat.com

Live

JivoChat API and MCP server

JivoChat has no API to read chats, list clients or merge duplicates, only webhooks that push new events. Sign in to JivoChat 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 JivoChat.

JivoChat has no API for this. So we run one for you.

JivoChat's own API, a GitHub MCP server and Cotlet compared
What you need JivoChat's APIGitHub MCP serverCotlet
Chats, clients, merges, reports No Partly Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when JivoChat changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 20, 2026. Sources: JivoChat Docs: Webhooks API · JivoChat Docs: Chat API · JivoChat Docs: Bot API · Zapier: JivoChat integrations

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

  1. 01Sign in to JivoChat in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect JivoChat to Claude, ChatGPT or my code?

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

For AI agents: MCP

Add Cotlet to your agent once. JivoChat 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/jivochat with its own method and path, such as POST /api/v1/jivochat/chats/{chat_id}/replies, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the JivoChat API and MCP server do?

13 tools on your own JivoChat account. Agents call them as operations of the MCP tools jivochat_read and jivochat_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
JivoChat tools in Cotlet's MCP server and REST API
Tool What it does Access
list_chats List chats from the Contact Center: Inbox, My dialogs, Archives or All, with an optional search. read
get_chat Read one chat: every message, the client details and the chat topic. read
list_clients List the clients in the CRM section with their tags, status and assigned agent. read
get_client Read one client: contact details, company, status, category, tags, description and chat list. read
list_duplicate_clients List the clients JivoChat flags as duplicates of one client. read
list_chat_topics List the chat topics your administrator set up, with their sub-topics. read
list_quick_phrases List the quick phrases your team shares, with their "/" shortcuts. read
get_aggregated_report Get accepted and missed chats and calls for a period, per channel and per agent. read
accept_chat Accept a waiting chat from the Inbox so it moves to My dialogs. writeasks first
reply_to_chat Send a text message to the client in a chat you accepted. writeasks first
set_chat_topic Label a chat with one of your chat topics, as an agent does in the About chat block. write
update_client_tags Add or remove tags on a client in the CRM section. write
merge_clients Merge a duplicate client into another and pick which side wins on the fields that differ. writeasks first

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All JivoChat use cases

Is it safe to connect JivoChat?

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 JivoChat 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 JivoChat 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 JivoChat have an API?

JivoChat has four developer APIs, Widget, Webhooks, Chat and Bot, but no REST API to read chats, clients or history, and no official MCP server (checked 20 Oct 2026). The Webhooks API pushes events such as chat_finished to your server. The Chat and Bot APIs connect your own channel or chatbot to JivoChat.

How do I get access?

Sign up free, open JivoChat 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 13 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 JivoChat yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so JivoChat 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: accept_chat, reply_to_chat, merge_clients wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agent read chats from before I connected?

Yes. list_chats reads the Archives and All tabs, and get_chat returns the full conversation. JivoChat's own Webhooks API cannot do this: its chat_finished event carries the transcript of a chat only when it ends, so a server of your own has to store each one as it happens.

Which JivoChat role does my account need?

It follows the app. Any agent can work chats and merge clients. The aggregated report is for administrators only, and chat topics are set up by an administrator before agents can pick one. A call your role cannot make fails with APP_PERMISSION_DENIED.

Should I use a JivoChat 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 JivoChat 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 JivoChat?

No. Cotlet is independent and not affiliated with JivoChat.

Give your agent access to JivoChat.

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

Sign up free