JivoChat MCP Server
Chats, clients, quick phrases and reports in JivoChat, worked by your agent.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/jivochat'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
JivoChat API and MCP server: Let your AI agent clear the JivoChat Inbox.
JivoChat has no MCP server and no REST API that lists chats, reads history, changes clients or returns statistics (checked 27 Oct 2026). Its Webhooks API pushes events to your server on PRO and VIP, and its Chat and Bot APIs connect your own channel or chatbot. Cotlet runs 13 JivoChat tools hosted, over MCP for agents and REST for scripts, in your own agent login.
Chats, clients, quick phrases and reports in JivoChat, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with JivoChat
- Page: https://cotlet.dev/integrations/jivochat-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by JivoChat. JivoChat is a trademark of its owner. If JivoChat's own integrations cover what you need, use them first.
What can you automate in JivoChat?
- Accept and answer waiting Inbox chats
- Reply in your team's quick phrases
- Merge clients who wrote twice
- Tag clients who asked about wholesale
- Set a chat topic on finished chats
- Count missed chats per agent
Does JivoChat have an MCP server or an API?
- Webhooks fire on chat_accepted, chat_finished, offline_message, client_updated and a few more. They report what just happened and cannot look anything up.
- Zapier has one trigger, New Chat Finished, and no actions, so Zapier MCP has nothing to call in JivoChat. Make only watches the same webhook.
- JivoChat's own AI Agent answers visitors from your knowledge files inside JivoChat. No outside agent can call it.
| What you need | Webhooks, Zapier, Make | Bot API | Cotlet |
|---|---|---|---|
| Read chats from before you connected | No, new events only | No | Yes, Archives and All |
| Answer a chat in the human Inbox | No | Only chats routed to your bot | Yes, as your agent, after your OK |
| List, tag and merge clients | Change events only | No | Yes |
| Missed chats per agent | No | No | Yes, administrator login |
| JivoChat plan needed | PRO or VIP | PRO for chatbots | Any |
| What you run | A server or a Zapier plan | A bot platform | Nothing |
Checked 27 Oct 2026. Sources: JivoChat: API for developers, JivoChat Docs: Webhooks API, JivoChat Docs: Bot API, Zapier: JivoChat triggers and actions, Make: JivoChat modules, JivoChat pricing
How does Cotlet connect to JivoChat?
- Sign in to JivoChat. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your JivoChat password, and no chat is accepted, answered or merged until you approve it.
Connect JivoChat to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Open JivoChat in a Cloud Browser. Create a Cotlet account, open JivoChat in its Cloud Browser, sign in with your own agent login (administrator if you want the aggregated report) and press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts pass an API key from the console.
JivoChat sits behind the same address, https://cotlet.dev/mcp/v1, as every app you enable on Cotlet. Turned JivoChat on after you connected? Refresh the connector and the 13 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: jivochat_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: jivochat_write
How to use the JivoChat REST API
Create your Cotlet API key
Create a Cotlet API key with access to JivoChat and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect JivoChat in Cotlet and enable it for agents. Account access: Your own JivoChat agent account (administrator for the aggregated report). You sign in once in your own Cloud Browser and keep your own settings.
Make your first JivoChat API request
REST:
curl https://cotlet.dev/api/v1/jivochat/clients \
-H "Authorization: Bearer $COTLET_API_KEY"
Read clients and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "jivochat",
"tool": "list_clients",
"result": {
"clients": [
{
"client_id": "cl_3a91",
"name": "Dana Whitfield",
"email": "dana@example.com",
"phone": "+1 555 0100",
"tags": [
"wholesale"
],
"status": "New",
"owner": "sam@example.com",
"conversations": 3
},
{
"client_id": "cl_7b20",
"name": "D. Whitfield",
"email": "dana@example.com",
"phone": null,
"tags": [],
"status": "New",
"owner": null,
"conversations": 1
}
],
"next_cursor": null
}
}
list_clients returns one page of the Clients list in CRM: name, email, phone, tags, status, the assigned agent and the number of conversations. The tag filter matches the tags your team already uses.
The cursor continues the same search.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
JivoChat workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | List the clients JivoChat flags as duplicates of one client. Use list_duplicate_clients in your configured support report. |
| Make | HTTP > Make a request | Read one chat: every message, the client details and the chat topic. Use get_chat in your configured support report. |
| Python or Node.js | REST API | Get accepted and missed chats and calls for a period, per channel and per agent. Use get_aggregated_report in your configured support report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads JivoChat; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
JivoChat API endpoints and MCP tools
Chats in the Contact Center
An Inbox chat has to be accepted before anyone can write in it, and a chat another agent took first fails without a change. Replies are text only and go out under your agent name.
- List chats (
list_chats, read): List chats from the Contact Center: Inbox, My dialogs, Archives or All, with an optional search. - Get a chat (
get_chat, read): Read one chat: every message, the client details and the chat topic. - Accept a chat (
accept_chat, write, asks first): Accept a waiting chat from the Inbox so it moves to My dialogs. - Reply to a chat (
reply_to_chat, write, asks first): Send a text message to the client in a chat you accepted.
Topics and quick phrases
Topics and phrases are the ones your administrator set up; quick phrases are shared by every operator, so the agent reads them and does not edit them.
- List chat topics (
list_chat_topics, read): List the chat topics your administrator set up, with their sub-topics. - Set a chat topic (
set_chat_topic, write): Label a chat with one of your chat topics, as an agent does in the About chat block. - List quick phrases (
list_quick_phrases, read): List the quick phrases your team shares, with their "/" shortcuts.
Clients in CRM
Duplicates are the ones JivoChat flags by a shared email or phone. A merge works inside one Live Chat channel and cannot be undone.
- List clients (
list_clients, read): List the clients in the CRM section with their tags, status and assigned agent. - Get a client (
get_client, read): Read one client: contact details, company, status, category, tags, description and chat list. - List duplicate clients (
list_duplicate_clients, read): List the clients JivoChat flags as duplicates of one client. - Update client tags (
update_client_tags, write): Add or remove tags on a client in the CRM section. - Merge duplicate clients (
merge_clients, write, asks first): Merge a duplicate client into another and pick which side wins on the fields that differ.
Statistics
Administrator logins only, up to 180 days per call. Other roles get APP_PERMISSION_DENIED.
- Get the aggregated report (
get_aggregated_report, read): Get accepted and missed chats and calls for a period, per channel and per agent.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/jivochat-api-mcp-server#tools
Who can see my JivoChat session, and how do I revoke it?
- What we store. Your signed-in JivoChat profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 13 JivoChat tools, never the session cookie.
- What the session sees. What your role sees: chats, client cards, emails, phones, tags.
- What no tool touches. Billing, plan, channels, team members, widget code, deletes.
- If JivoChat signs you out. You sign in again yourself, in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser, or change your JivoChat password.
Visitors type order numbers, addresses and phone numbers into chat, so the agent reads them as your agents do. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Lists the Inbox. Live chats and offline messages, every page.
- Reads each chat. The whole log and the client card first.
- Picks a quick phrase. Refunds and complaints stay with you.
- Waits, then sends. Accept and reply show up in your Cotlet console first.
| Action | Undo |
|---|---|
| Set a chat topic | Yes, set another topic |
| Add or remove client tags | Yes, one more call |
| Accept a chat | The chat stays yours; another agent can take it over in JivoChat |
| Reply to a chat | No, the visitor sees it at once |
| Merge clients | No, JivoChat cannot reverse a merge |
3 of 13 tools ask first: accept_chat, reply_to_chat and merge_clients. A topic or a tag reaches nobody outside your team, so those run at once. For a quick phrase you send fifty times a week, you can turn the wait off on reply_to_chat.
Leave the wait on for merge_clients. Two people who share a company mailbox look like one duplicate, and only the side you keep wins on name, company and status.
MCP call:
{
"name": "reply_to_chat",
"arguments": {
"chat_id": "6f1a2b3c",
"text": "Yes, it is in stock and ships within one business day."
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/jivochat/chats/6f1a2b3c/replies \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Yes, it is in stock and ships within one business day."}'
Response:
{
"chat_id": "6f1a2b3c",
"message_id": "m_5d21",
"status": "sent",
"sent_at": "2026-10-19T09:44:10Z"
}
A cron job or an n8n flow calls the same tools over REST at /api/v1/jivochat with the same key and price, for example get_aggregated_report every Monday at 8 am into a Slack message. A reply to a chat nobody accepted fails, and failed calls are free. Each tool row above shows its REST path.
How much does the JivoChat MCP server cost?
About $49 a month for an online shop with 3 JivoChat agents, 8,440 credits. Chat tools work on Free, client tools from Basic, where the CRM starts; webhooks would need PRO or VIP.
| Job | Calls | Credits |
|---|---|---|
| Morning Inbox and offline messages, daily | 9 × 30 | 2,700 |
| Chat topics on finished chats, each workday | 14 × 22 | 3,080 |
| Tag clients who asked about wholesale, weekly | 12 × 4 | 480 |
| Merge duplicate clients, weekly | 15 × 4 | 600 |
| Missed chats report, Mondays | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 8,440 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Chats on every plan, clients from Basic (the CRM)
JivoChat reviewers describe teams of under 5 agents, and JivoChat publishes no chat counts, so the month is our example. For scale, Basic for 3 agents is $84 a month billed yearly ($28 an agent), Professional $126. Dollars at the $29 pack rate.
JivoChat MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| theYahia/jivosite-mcp | 10 tools for chats, agents, contacts and messages, npm package, MIT, 0 stars. | Calls api.jivosite.com/v1 with a token; that REST API is not in JivoChat's docs. Last push 5 Sep 2026. |
| fixesS/jivo-lib | Library for bots on the JivoChat Bot API, 7 stars. | Bot side only, not the human Inbox or CRM; last push 5 Sep 2022. |
| Zapier and Make | Start a workflow when a chat finishes. | No JivoChat actions; webhooks need PRO or VIP. |
| JivoChat AI Agent | Answers visitors from your knowledge files inside JivoChat. | No outside agent can call it; does not merge, tag or report. |
If you want a bot that greets every visitor before a person does, JivoChat's own AI Agent or a Bot API platform fits better. For the agent desk itself, from a full Inbox to Monday's missed-chat count, Cotlet works in the JivoChat login you already use.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the JivoChat tools go to contact@cotlet.dev.
JivoChat API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open JivoChat under Integrations in the console and sign in to JivoChat in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect JivoChat to ChatGPT or Claude?
Sign up at cotlet.dev, log in to JivoChat once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your JivoChat account through Cotlet, in their phone apps too.
What can ChatGPT do in JivoChat?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in JivoChat: answer new chats from the Inbox; merge duplicate clients; weekly missed chats and agent report. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Do I need JivoChat PRO for this?
No. PRO or VIP is what JivoChat asks for webhooks and chatbot integration. Cotlet works on any plan within what it includes: the CRM, for example, starts on Basic.
Can it answer the moment a chat comes in?
Cotlet has no JivoChat trigger. Run your agent on a schedule, every 15 minutes for example, or on PRO let the New Chat Finished webhook start a flow for chats that just ended.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 13 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with JivoChat?
No. Cotlet is independent and not affiliated with JivoChat or LLC Tecnology Distribution Ltda.
Can I use the JivoChat API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.