Tidio
Customer supportLive chat and helpdesk with Lyro, an AI support agent. Lyro can connect to external MCP servers to use their tools, and Tidio publishes an Analytics MCP.
Independent review. Unpaid; no partnership with Chatbase. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Builds AI support agents that answer from your content and can be embedded on a website. Its remote MCP server lets authorized assistants manage agents and knowledge sources, read conversations and handle help desk tickets. API access is listed on Standard and higher plans.
Judgment, not a score. Documentation checked 2026-10-18.
Connections: MCP connections · APIs · Portability and vendor lock-in.
Advertised dollar rates: Hobby is $32/month billed annually or $40 monthly; Standard $120/month billed annually or $150 monthly; Pro $400/month billed annually or $500 monthly. Monthly message-credit allowances are 700, 4,000 and 15,000 respectively. Standard adds API access. Enterprise is quoted separately. Auto-recharge credits cost $40 per 1,000; confirm tax and currency terms at checkout. source ↗
Server Custom Actions call external APIs and use JSON request/response data; other action types can run client code or display widgets. Webhooks are configured on lead or custom-form actions, while phone-call summaries have channel-level webhook settings. Check credentials, event signatures and the permitted actions before connecting live systems. source ↗
The remote MCP server documents Claude, ChatGPT, Codex and Cursor with OAuth 2.1. Source changes can take effect immediately. Client permission settings can hide destructive tools; review edits and deletion permissions before use. source ↗
How Chatbase connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Setup steps in Chatbase's MCP docs. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Chatbase named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Chatbase publishes an API, but this pairing still needs network, authentication and execution-scope checks. Chatbase API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Chatbase is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Chatbase's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Chatbase file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Setup steps in Chatbase's MCP docs. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Chatbase named integration docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Chatbase publishes an API, but this pairing still needs network, authentication and execution-scope checks. Chatbase API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Chatbase is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Chatbase's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Chatbase file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Chatbase has an official MCP server and Google Antigravity supports MCP, but Chatbase's docs don't name this pairing. Auth setup may differ. Chatbase MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Chatbase publishes an API, but this pairing still needs network, authentication and execution-scope checks. Chatbase API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Chatbase is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Chatbase's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Chatbase file docs ↗Google Antigravity file docs ↗ |
Chatbase's docs also name: ChatGPT.
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ (Standard and higher according to the pricing table) |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ (selectable-text PDF, TXT, DOC and DOCX; scanned PDFs need a text layer) |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
No long-form review yet. Verdict is based on research, not hands-on testing.
Live chat and helpdesk with Lyro, an AI support agent. Lyro can connect to external MCP servers to use their tools, and Tidio publishes an Analytics MCP.
Customer messaging and help desk with Fin AI. Its hosted MCP server supports US/EU workspaces, including conversation/contact retrieval, help-center article writes and internal notes. Eligible workspaces can also delegate to Fin Operator.