# Chatbase: MCP server status, API access gate and what it does > No-code AI agent builder for deploying chat/voice/email support-and-sales bots across a website widget and... No MCP found, Paid, self-serve. 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) / Chatbase # Chatbase [No MCP found](../mcp/none-found.md) [Paid, self-serve](../gates/paid.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: [chatbase.co](https://chatbase.co) · entry id 14-chatbase · source 14-inbound-plg-chat.md line 84 **What it does** No-code AI agent builder for deploying chat/voice/email support-and-sales bots across a website widget and channels like WhatsApp and Slack. **AI features, separated from automation with an AI label on it** Lets a builder pick from multiple underlying LLMs (Claude, Gemini, GPT, DeepSeek referenced on the site) and wire up "Actions" (order lookups, invoice retrieval, payment processing) plus a testing sandbox before going live - genuine AI-agent orchestration tooling, though conversation quality depends entirely on the connected model rather than a proprietary Chatbase model. **RevOps role** Solo-operator-friendly, self-serve chatbot-builder entry point into inbound AI chat - cheaper and more accessible than most enterprise tools in this category, at the cost of no proprietary conversation-intelligence 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**: Paid, self-serve - **Can a solo operator reach it**: Yes, by paying, no sales call api_gate, verbatim from the file: paid (limited free tier). Free plan: $0/mo, 50 message credits, inactive agents deleted after 14 days, no API access. API access starts at the Standard tier ($150/mo); Hobby ($40/mo) does not include it. **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.chatbase.co](https://www.chatbase.co) - [https://www.chatbase.co/pricing](https://www.chatbase.co/pricing) - [https://www.chatbase.co/docs](https://www.chatbase.co/docs) 3 source URLs. Raw sources field, verbatim: https://www.chatbase.co, https://www.chatbase.co/pricing, https://www.chatbase.co/docs **Notes, verbatim from the file** Checked mcp.so, glama.ai, and PulseMCP directly for a Chatbase MCP server - PulseMCP returned zero results ("Showing 0-0 of 0 servers"). Domain is chatbase.co (not .com); no redirect was observed. **Provenance** - **Entry id**: 14-chatbase - **Source file**: 14-inbound-plg-chat.md - **Source line**: 84 - **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).