# Tidio: MCP server status, API access gate and what it does > Customer-service platform combining live chat, a help desk, and an AI agent ("Lyro") that resolves routine... No MCP found, Free to start. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [Inbound & PLG Chat](../categories/inbound-plg-chat.md) / Tidio # Tidio [No MCP found](../mcp/none-found.md) [Free to start](../gates/free.md) [Inbound & PLG Chat](../categories/inbound-plg-chat.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [tidio.com](https://tidio.com) · entry id 14-tidio · source 14-inbound-plg-chat.md line 237 **What it does** Customer-service platform combining live chat, a help desk, and an AI agent ("Lyro") that resolves routine support/sales questions automatically. **AI features, separated from automation with an AI label on it** Lyro AI Agent is marketed to resolve "up to 90%" of low-level questions with an "80% resolution rate across 10,000 chats a month," answering in the brand's voice with context awareness - vendor-stated figures, not independently verified. **RevOps role** Widely deployed (300,000+ businesses per vendor) SMB-friendly inbound chat/support layer. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Access gate** - **Gate bucket**: Free to start - **Can a solo operator reach it**: Yes, without talking to anyone api_gate, verbatim from the file: free (limited). Self-serve, no-card-required free tier exists; a "Premium Plan" and enterprise options are directed to sales for pricing. **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **Jobs it can do** - [Answer an inbound chat or call](../jobs/answer-inbound-chat.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://www.tidio.com](https://www.tidio.com) 1 source URL. Thin. The standing rule is at least two independent sources with the vendor's own site unable to be both of them, and this entry does not meet it. 32 entries are in the same state and they are listed on the methodology page. Raw sources field, verbatim: https://www.tidio.com **Notes, verbatim from the file** Tidio's own marketing copy lists "REST APIs, webhooks, JS actions, or Model Context Protocol (MCP)" as supported integration methods, but no dedicated MCP docs page, repo, or listing could be located on tidio.com, PulseMCP, mcp.so, or glama.ai during this research pass - per this directory's law that an MCP claim requires a URL in hand, this is logged as none-found rather than official/community despite the vendor's own claim. Re-check before the next pass. **Provenance** - **Entry id**: 14-tidio - **Source file**: 14-inbound-plg-chat.md - **Source line**: 237 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).