# Clara (Clara Labs): MCP server status, API access gate and what it does > AI scheduling assistant reached by CC'ing "Clara" on an email thread - it reads the thread, proposes times,... 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) / [Scheduling & Routing](../categories/scheduling-routing.md) / Clara (Clara Labs) # Clara (Clara Labs) [No MCP found](../mcp/none-found.md) [Paid, self-serve](../gates/paid.md) [Scheduling & Routing](../categories/scheduling-routing.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: [claralabs.com](https://claralabs.com) · entry id 10-clara · source 10-scheduling-routing.md line 236 **What it does** AI scheduling assistant reached by CC'ing "Clara" on an email thread - it reads the thread, proposes times, handles replies, and confirms meetings across Google Workspace, Outlook, Zoom, and Teams without a human doing the back-and-forth. **AI features, separated from automation with an AI label on it** The core mechanism (reading email threads, proposing/negotiating times, confirming) plausibly requires real NLP, but Clara Labs discloses no model details publicly. The vendor states "no human at Clara reads your emails," implying full automation - a vendor privacy claim, not an independently verified capability breakdown. **RevOps role** Adjacent to core GTM stacks - most naturally an EA/executive-scheduling tool (vendor's own listed segments are recruiters, legal/finance, executives, founders, agencies) rather than a rep-facing prospect-booking tool, included here as a genuinely AI-driven scheduling-negotiation product worth knowing about. **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: n/a **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 - a 14-day free trial exists (5 meetings) but there is no perpetual free tier; Standard is $80/month (30 meetings), Enterprise is contact-sales for unlimited/company-wide use. **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** - [Book a meeting](../jobs/book-a-meeting.md) - [Read calendar availability](../jobs/read-calendar-availability.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://claralabs.com](https://claralabs.com) - [https://claralabs.com/pricing](https://claralabs.com/pricing) - [https://www.pulsemcp.com](https://www.pulsemcp.com) - searched "clara" - zero relevant results 3 source URLs. Raw sources field, verbatim: https://claralabs.com, https://claralabs.com/pricing, https://www.pulsemcp.com (searched "clara", zero relevant results) **Notes, verbatim from the file** No mention of API or MCP access anywhere on the public site or in MCP registries (mcp.so, glama.ai, pulsemcp.com all returned nothing relevant for "Clara" scheduling). **Provenance** - **Entry id**: 10-clara - **Source file**: 10-scheduling-routing.md - **Source line**: 236 - **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).