[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # JivoChat API and MCP server > 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. Live chat and business messenger for websites: visitors write in a widget, agents answer in one Contact Center, and a CRM keeps clients, tags and conversation history. ## What is the JivoChat API? Cotlet's JivoChat API exposes 13 endpoints for your own JivoChat account: list chats, get a chat, list clients, get a client, list duplicate clients, list chat topics, list quick phrases, get the aggregated report, accept a chat, reply to a chat, set a chat topic, update client tags and merge duplicate clients. The list_chats endpoint returns list chats from the Contact Center: Inbox, My dialogs, Archives or All, with an optional search. Each endpoint takes simple JSON inputs like chat_id, client_id or query and works both as an operation of the jivochat_read or jivochat_write MCP tool for agents and as a REST call for scripts. - **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md) - **Endpoints:** 13 (8 read, 5 write) - **Updated:** 2026-10-19 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). Cotlet is a hosted MCP server and REST API for JivoChat with 13 endpoints (8 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does JivoChat have an official 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. | Task | JivoChat official | Cotlet | |---|---|---| | Read chats and their history | Partly: The chat_finished webhook sends the transcript of each new finished chat; nothing returns chats from before you started storing them | Yes | | Reply to a visitor as an agent | Partly: The Bot API and the Chat API send messages for chats on a channel or a bot you connect, not in your agents' own Inbox | Yes | | Accept a chat from the Inbox | No | Yes | | List clients with tags, status and owner | No | Yes | | Add or remove client tags | No | Yes | | Merge duplicate clients | No | Yes | | Label chats with chat topics | No | Yes | | Aggregated report of accepted and missed chats | No | Yes | Sources: [JivoChat Docs: Webhooks API](https://www.jivochat.com/docs/webhooks/), [JivoChat Docs: Chat API](https://www.jivochat.com/docs/chat/), [JivoChat Docs: Bot API](https://www.jivochat.com/docs/bot/), [Zapier: JivoChat integrations](https://zapier.com/apps/jivochat/integrations) ## For AI agents ```text 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. Cotlet provides a hosted MCP server and REST API for JivoChat: 13 tools (8 read, 5 write). Access Sign up at https://cotlet.dev/app/signup?app=jivochat, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools jivochat_read, jivochat_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/jivochat, each operation at its own route, e.g. POST /api/v1/jivochat/chats/{chat_id}/replies Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_chats, get_chat, list_clients, get_client, list_duplicate_clients, list_chat_topics, list_quick_phrases, get_aggregated_report, accept_chat, reply_to_chat, set_chat_topic, update_client_tags, merge_clients Confirm accept_chat, reply_to_chat, merge_clients (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/jivochat-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=jivochat, requests JivoChat in the Cotlet console and creates an API key there. 2. The user signs in to JivoChat once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables JivoChat for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted JivoChat server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source JivoChat MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to JivoChat in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get JivoChat only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no JivoChat login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following JivoChat's terms; Cotlet is not affiliated with JivoChat. ``` ## What can an AI agent do in JivoChat? Cotlet is best for support teams on JivoChat who want an AI agent to answer waiting chats, tidy the client list and report missed chats without running or fixing a server. - **[Answer new chats from the Inbox](https://cotlet.dev/integrations/jivochat-api-mcp-server/answer-new-chats-from-inbox.md)**: "Look at the JivoChat Inbox. For each new chat, accept it and reply with the matching quick phrase if there is one. Leave anything about refunds or complaints for me and tell me why." → `list_chats`, `get_chat`, `list_quick_phrases`, `accept_chat`, `reply_to_chat` - **[Merge duplicate clients](https://cotlet.dev/integrations/jivochat-api-mcp-server/merge-duplicate-clients.md)** (runs: weekly): "Find JivoChat clients that share an email with another client. For each pair, keep the older client, take the name and company from whichever side has them, and merge." → `list_clients`, `list_duplicate_clients`, `get_client`, `merge_clients` - **[Weekly missed chats and agent report](https://cotlet.dev/integrations/jivochat-api-mcp-server/weekly-missed-chats-report.md)** (runs: weekly): "Every Monday, pull last week's JivoChat aggregated report and tell me accepted and missed chats for the account and for each agent." → `get_aggregated_report` - **Label finished chats with a topic** (runs: daily): "Go through yesterday's finished JivoChat chats with no topic and set the best matching chat topic on each." → `list_chats`, `get_chat`, `list_chat_topics`, `set_chat_topic` - **Tag clients who ask about wholesale**: "Find JivoChat clients whose chats mention wholesale or bulk pricing and add the tag wholesale." → `list_clients`, `get_client`, `get_chat`, `update_client_tags` ## Can JivoChat automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a JivoChat connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to merge duplicate clients, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/jivochat/clients. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/jivochat/clients with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to JivoChat. ### list_chats List chats from the Contact Center: Inbox, My dialogs, Archives or All, with an optional search. Access: read. REST: `GET /api/v1/jivochat/chats`. MCP: `jivochat_read → list_chats`. | Parameter | Type | Required | Description | |---|---|---|---| | `tab` | string | yes | Contact Center tab: inbox, my_dialogs, archives or all. | | `query` | string | no | Search text, the same search as at the top of the Archives tab. | | `cursor` | string | no | Next page cursor from the previous call. | list_chats returns one page of chats with the client name, the channel, the start time and a preview of the last message. The inbox tab shows chats no agent has accepted yet. Finished chats in archives also carry their duration. The cursor continues the same tab and search. What you see follows your role and the channels your account can open. Example response: ```json { "chats": [ { "chat_id": "6f1a2b3c", "client_name": "Dana Whitfield", "channel": "Live Chat", "tab": "inbox", "preview": "Is the 12-inch model in stock?", "started_at": "2026-10-19T09:41:00Z" }, { "chat_id": "9c4d5e6f", "client_name": "Visitor from Lisbon", "channel": "Live Chat", "tab": "inbox", "preview": "Offline message: can you call me back about my order?", "started_at": "2026-10-19T07:12:00Z" } ], "next_cursor": null } ``` ### get_chat Read one chat: every message, the client details and the chat topic. Access: read. REST: `GET /api/v1/jivochat/chats/{chat_id}`. MCP: `jivochat_read → get_chat`. | Parameter | Type | Required | Description | |---|---|---|---| | `chat_id` | string | yes | Chat ID from list_chats. | get_chat returns the whole conversation in the order it happened, each message with who wrote it (client, agent or bot), the text and the time. It also returns the client card the app shows next to the chat and the chat topic, if an agent set one. Files and photos come back as links, not as content. Example response: ```json { "chat_id": "6f1a2b3c", "channel": "Live Chat", "client": { "client_id": "cl_3a91", "name": "Dana Whitfield", "email": "dana@example.com" }, "topic": null, "messages": [ { "from": "client", "text": "Is the 12-inch model in stock?", "sent_at": "2026-10-19T09:41:00Z" }, { "from": "bot", "text": "One moment, I am looking for an agent.", "sent_at": "2026-10-19T09:41:04Z" } ] } ``` ### list_clients List the clients in the CRM section with their tags, status and assigned agent. Access: read. REST: `GET /api/v1/jivochat/clients`. MCP: `jivochat_read → list_clients`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | no | Search text: name, email or phone. | | `tag` | string | no | Only clients with this tag. | | `cursor` | string | no | Next page cursor from the previous call. | 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. Example response: ```json { "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 } ``` ### get_client Read one client: contact details, company, status, category, tags, description and chat list. Access: read. REST: `GET /api/v1/jivochat/clients/{client_id}`. MCP: `jivochat_read → get_client`. | Parameter | Type | Required | Description | |---|---|---|---| | `client_id` | string | yes | Client ID from list_clients. | get_client returns the client card from CRM and the chats this client had, so an agent sees the full conversation history before it writes. Chat IDs in the list open with get_chat. Example response: ```json { "client_id": "cl_3a91", "name": "Dana Whitfield", "email": "dana@example.com", "company": "Whitfield Supply", "status": "New", "category": null, "tags": [ "wholesale" ], "description": "Asked about bulk pricing.", "owner": "sam@example.com", "chats": [ { "chat_id": "6f1a2b3c", "channel": "Live Chat", "started_at": "2026-10-19T09:41:00Z" } ] } ``` ### list_duplicate_clients List the clients JivoChat flags as duplicates of one client. Access: read. REST: `GET /api/v1/jivochat/clients/{client_id}/duplicate-clients`. MCP: `jivochat_read → list_duplicate_clients`. | Parameter | Type | Required | Description | |---|---|---|---| | `client_id` | string | yes | Client ID from list_clients. | list_duplicate_clients returns the same list the red icon next to the client data opens in the app: customers who share an email or phone number with this one. Each entry shows the fields you choose between when you merge. The list is empty when the client has no duplicate. Example response: ```json { "client_id": "cl_3a91", "duplicates": [ { "client_id": "cl_7b20", "name": "D. Whitfield", "email": "dana@example.com", "company": null, "status": "New", "category": null, "description": null } ] } ``` ### list_chat_topics List the chat topics your administrator set up, with their sub-topics. Access: read. REST: `GET /api/v1/jivochat/chat-topics`. MCP: `jivochat_read → list_chat_topics`. No parameters. list_chat_topics returns the topics from the Chat Topics button in the Contact Center, nested as the administrator built them. It returns an empty list when the account has no topics. Use the IDs with set_chat_topic. Example response: ```json { "topics": [ { "topic_id": "tp_01", "name": "Orders", "children": [ { "topic_id": "tp_02", "name": "Delivery" }, { "topic_id": "tp_03", "name": "Returns" } ] }, { "topic_id": "tp_04", "name": "Pricing", "children": [] } ] } ``` ### list_quick_phrases List the quick phrases your team shares, with their "/" shortcuts. Access: read. REST: `GET /api/v1/jivochat/quick-phrases`. MCP: `jivochat_read → list_quick_phrases`. No parameters. list_quick_phrases returns every quick phrase of the account, each with its shortcut tag and its text. Quick phrases are shared by all operators, so the list is the same for every agent. An agent reads them before it writes, so replies use your wording. Example response: ```json { "phrases": [ { "phrase_id": "qp_11", "shortcut": "/stock", "text": "Yes, it is in stock and ships within one business day." }, { "phrase_id": "qp_12", "shortcut": "/callback", "text": "Thanks for your message. Please send your phone number and a good time, and we will call you." } ] } ``` ### get_aggregated_report Get accepted and missed chats and calls for a period, per channel and per agent. Access: read. REST: `GET /api/v1/jivochat/aggregated-report`. MCP: `jivochat_read → get_aggregated_report`. | Parameter | Type | Required | Description | |---|---|---|---| | `date_from` | string | yes | First day of the period, YYYY-MM-DD. | | `date_to` | string | yes | Last day of the period, YYYY-MM-DD. | get_aggregated_report returns the numbers of Statistics > Aggregated Report: accepted chats, accepted calls, missed chats and missed calls, once for the whole account, once per agent and once per agent in each channel. The app allows a period of up to 180 days, and its help center advises 90 days at most. Only an administrator can open this report; any other role gets APP_PERMISSION_DENIED. Example response: ```json { "period": { "date_from": "2026-10-12", "date_to": "2026-10-18" }, "by_sites": [ { "channel": "Live Chat", "accepted_chats": 118, "accepted_calls": 0, "missed_chats": 9, "missed_calls": 0 } ], "by_agents": [ { "agent": "Sam Rivera", "accepted_chats": 71, "accepted_calls": 0 }, { "agent": "Priya Nair", "accepted_chats": 47, "accepted_calls": 0 } ], "by_agents_per_site": [ { "channel": "Live Chat", "agent": "Sam Rivera", "accepted_chats": 71, "accepted_calls": 0 }, { "channel": "Live Chat", "agent": "Priya Nair", "accepted_chats": 47, "accepted_calls": 0 } ] } ``` ### accept_chat Accept a waiting chat from the Inbox so it moves to My dialogs. Access: write, asks the user first. REST: `POST /api/v1/jivochat/chats/{chat_id}/accept`. MCP: `jivochat_write → accept_chat`. | Parameter | Type | Required | Description | |---|---|---|---| | `chat_id` | string | yes | Chat ID from list_chats. | accept_chat takes a chat no agent has accepted yet and makes you its agent, so the client sees that someone is there. A chat that another agent accepted first fails with a clear error and nothing changes. After it, reply_to_chat can write in the chat. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "chat_id": "6f1a2b3c", "status": "accepted", "tab": "my_dialogs" } ``` ### reply_to_chat Send a text message to the client in a chat you accepted. Access: write, asks the user first. REST: `POST /api/v1/jivochat/chats/{chat_id}/replies`. MCP: `jivochat_write → reply_to_chat`. | Parameter | Type | Required | Description | |---|---|---|---| | `chat_id` | string | yes | Chat ID from list_chats. | | `text` | string | yes | Message text, plain text. | reply_to_chat sends one message under your agent name in a chat in My dialogs. The client sees it at once. It sends text only: no files or photos. A chat in the Inbox must be accepted first with accept_chat. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "chat_id": "6f1a2b3c", "message_id": "m_5d21", "status": "sent", "sent_at": "2026-10-19T09:44:10Z" } ``` ### set_chat_topic Label a chat with one of your chat topics, as an agent does in the About chat block. Access: write. REST: `PUT /api/v1/jivochat/topics/{topic_id}/chats/{chat_id}/topic`. MCP: `jivochat_write → set_chat_topic`. | Parameter | Type | Required | Description | |---|---|---|---| | `chat_id` | string | yes | Chat ID from list_chats. | | `topic_id` | string | yes | Topic ID from list_chat_topics. | set_chat_topic sets the topic that the Statistics section counts in its chat topics tab. A topic that does not exist fails at once and the error lists the account's topics. The label reaches nobody outside your team and calling it again with another topic changes it, so it does not wait for your OK. Example response: ```json { "chat_id": "6f1a2b3c", "topic": { "topic_id": "tp_01", "name": "Orders" } } ``` ### update_client_tags Add or remove tags on a client in the CRM section. Access: write. REST: `PATCH /api/v1/jivochat/clients/{client_id}/tags`. MCP: `jivochat_write → update_client_tags`. | Parameter | Type | Required | Description | |---|---|---|---| | `client_id` | string | yes | Client ID from list_clients. | | `add_tags` | string[] | no | Tags to add. | | `remove_tags` | string[] | no | Tags to remove. | update_client_tags changes only the tags you name and leaves the rest of the client card alone. Tags are how managers pick which clients to work on each day, so a rule such as "tag every client who asked about wholesale" feeds that list. The change reaches nobody outside your team and one more call undoes it, so it does not wait for your OK. Example response: ```json { "client_id": "cl_3a91", "tags": [ "wholesale", "follow-up" ] } ``` ### merge_clients Merge a duplicate client into another and pick which side wins on the fields that differ. Access: write, asks the user first. REST: `POST /api/v1/jivochat/duplicates/{duplicate_id}/clients/{client_id}/merge`. MCP: `jivochat_write → merge_clients`. | Parameter | Type | Required | Description | |---|---|---|---| | `client_id` | string | yes | The client you keep, from list_clients. | | `duplicate_id` | string | yes | The duplicate, from list_duplicate_clients. | | `keep_from` | string | no | Which client wins on Name, Company, Responsible, Status, Category and Description: client or duplicate. Default client. | merge_clients runs the Merge dialog of the app. Tags, tasks and deals are combined; the six fields come from the side you pick. The chat histories become one common chat, and later agent replies go to every device the customer used. The app cannot undo a merge, and it works only inside one channel and only in Live Chat channels. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "status": "merge_started", "client_id": "cl_3a91", "merged_client_id": "cl_7b20", "message": "The clients merge started" } ``` ## How do I connect JivoChat to Claude Code, Codex or Cursor? Connecting JivoChat takes three steps: sign up, sign in to JivoChat once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect JivoChat to your agent. 1. **Create an account** Sign up and add JivoChat in the console. Your API key is there too. 2. **Sign in to JivoChat in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to JivoChat there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. 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" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the JivoChat tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Look at the JivoChat Inbox. For each new chat, accept it and reply with the matching quick phrase if there is one. Leave anything about refunds or complaints for me and tell me why. ``` ### Call JivoChat from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/jivochat with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` 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."}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "chat_id": "6f1a2b3c", "message_id": "m_5d21", "status": "sent", "sent_at": "2026-10-19T09:44:10Z" } ``` ## Why use Cotlet for JivoChat? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to JivoChat yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When JivoChat changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect JivoChat to Cotlet? Yes. You sign in to JivoChat yourself, in your own Cloud Browser, and we never save your password. Your agents only get JivoChat once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **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 this an official JivoChat integration?** No, Cotlet is independent of JivoChat. JivoChat's own API is too limited for this work. Cotlet works through your own JivoChat account, the way you use JivoChat in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to JivoChat in your console: your agents lose access at once and you stay signed in. Signing out of JivoChat in the browser works too, and Reset browser deletes the whole profile. ## Is there a JivoChat MCP server on GitHub? Yes. A community JivoChat MCP server exists on GitHub, built by one developer. You install it on your own computer and keep it running yourself, and when JivoChat changes, it stops working until you or its maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Clone the repo, install it, connect it to JivoChat, add it to each MCP client | Sign up, sign in to JivoChat once, add one MCP server or API key | | When JivoChat changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free | | Your JivoChat session | In a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When the session expires | Tools fail until you sign in again by hand | Your Cloud Browser keeps you signed in; if JivoChat logs you out, your agent gets a link to sign in again | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when JivoChat changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the JivoChat API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the JivoChat API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | 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. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own JivoChat account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to JivoChat yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get JivoChat only after you enable it. When JivoChat signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to JivoChat, sign out of JivoChat in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **JivoChat's terms:** You use your own JivoChat account and stay responsible for following JivoChat's terms. Cotlet is independent and not affiliated with JivoChat. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open JivoChat in the console and press Request access. Then you create your API key and connect JivoChat there. **Do I need to be technical?** No. You sign in to JivoChat once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect JivoChat to Cotlet?** Yes. You sign in to JivoChat yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JivoChat once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My JivoChat sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your JivoChat cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through JivoChat's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. JivoChat sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no JivoChat login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** JivoChat offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **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. **Can my agent post or send messages in JivoChat without asking me?** No. Every call to accept_chat, reply_to_chat or merge_clients waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. set_chat_topic, update_client_tags runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the JivoChat API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/jivochat from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) 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. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.