IonBin
All pages
Search

Tidio

Customer support
Support MCPAPI/CLIFile import

Independent review. Unpaid; no partnership with Tidio. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

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.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
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.
Differentiation
Documented fit: Small businesses adding an AI agent to website chat. Uniqueness is not established.
Replaceability and switching
Compare Intercom, Chatbase. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Enabling customer-facing actions before validating identity checks, tool permissions and escalation behavior. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Best for
  • Small businesses adding an AI agent to website chat
Not for
  • Enabling customer-facing actions before validating identity checks, tool permissions and escalation behavior

Top use cases

  • Connect Lyro to external MCP servers so it can look up data and take actions source ↗
  • Pull support analytics into an AI assistant (Analytics MCP) source ↗

In depth

Support and AI quotas

The annual view lists Starter $24.17/month, Growth from $49.17 and Plus from $300 plus monthly usage; Premium is quoted. Free has 50 billable support conversations. The first 50 Lyro AI conversations are a lifetime allowance, not a monthly renewal. Paid Lyro quotas and Flows usage are separate; check the selected billing term and quota at checkout. source ↗

Two MCP directions

Lyro is an MCP client: connect an external server, inspect its tools and choose which Lyro may use in customer conversations. Limit access to appropriate lookups/actions and test identity checks and handoff before enabling writes. source ↗

Analytics server

Tidio's separate Analytics MCP is read-only and cannot send messages or change settings. It uses OpenAPI Client ID/Secret credentials and shares API permissions, freshness and rate limits. The documented ChatGPT integration specifically uses desktop Codex/Work configuration; this does not establish ordinary web-chat compatibility. source ↗

Knowledge imports

CSV Q&A uploads allow up to 500 entries per file and 10,000 total; PDF uploads allow up to 10 files at once. Review generated answers before use. Re-syncing a website replaces its Q&A pairs and removes manual edits; automatic weekly website sync requires an eligible Plus/Premium package. source ↗

How to use it with AI

How Tidio connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented Analytics MCP setup for Claude Code/Desktop. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Tidio named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Tidio publishes an API, but this pairing still needs network, authentication and execution-scope checks. Tidio API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Tidio 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. Tidio'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. Tidio file docs ↗Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented The ChatGPT Desktop guide explicitly configures local Codex/Work. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Tidio named integration docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Tidio publishes an API, but this pairing still needs network, authentication and execution-scope checks. Tidio API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Tidio 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. Tidio's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Tidio file docs ↗OpenAI Codex file docs ↗
Google Antigravity Not documented Tidio has an official MCP server and Google Antigravity supports MCP, but Tidio's docs don't name this pairing. Auth setup may differ. Tidio MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks Tidio publishes an API, but this pairing still needs network, authentication and execution-scope checks. Tidio 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. Tidio 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. Tidio's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Tidio file docs ↗Google Antigravity file docs ↗

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.

To verify External Lyro MCP transport/authentication and plan-specific availability require confirmation in the account; the release announcement does not specify them.

Agent compatibility

MCPAPI/CLIFile import
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗
API / CLIYes Official docs ↗
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importYes Official docs ↗

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

Connection capabilities to compare

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.

Workflows using this tool

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

Intercom

Customer support

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.

MCPAPI/CLIFile import
Support

Chatbase

Customer support

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.

MCPAPI/CLIFile import
Support