# Clari Copilot: MCP server status, API access gate and what it does > Records and transcribes sales calls in real time and surfaces live coaching prompts, deal-risk flags, and... Community MCP, 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) / [Conversation Intel](../categories/conversation-intel.md) / Clari Copilot # Clari Copilot [Community MCP](../mcp/community.md) [Paid, self-serve](../gates/paid.md) [Conversation Intel](../categories/conversation-intel.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: [clari.com/products/copilot/](https://clari.com/products/copilot/) · entry id 03-clari-copilot · source 03-conversation-intel.md line 49 **What it does** Records and transcribes sales calls in real time and surfaces live coaching prompts, deal-risk flags, and auto-generated CRM updates during and after the call. **AI features, separated from automation with an AI label on it** Real-time deal-risk / blocker and competitor-mention detection; automatic capture of intent, objections, contacts, and next steps for CRM writeback; AI-generated call summaries and follow-up emails. Live "battlecards"/playbooks are more rules-based coaching content than a distinct AI model. **RevOps role** Conversation-intelligence / call-recording layer (Gong-equivalent within the Clari family), feeding call-derived signals up into the broader Clari forecasting platform. **MCP server** - **Status bucket**: Community MCP - **Auth**: Scalekit-hosted connector uses per-user delegated OAuth-style authorization in Scalekit's own token vault. The underlying Clari Copilot REST API (https://api-doc.copilot.clari.com/) uses a static API Key + API Password pair generated in Workspace Settings → Integrations. - **Parsed URLs**: 2 found in the mcp_url field A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: community mcp_url, verbatim from the file: https://www.scalekit.com/connectors/claricopilot (third-party connector, not vendor-built). A Clari community forum thread - https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980 - asks why a "Copilot MCP Server" was pulled from July release notes, suggesting an official one may have been planned or briefly shipped; status of any first-party version is unresolved as of this research, so it is logged as community, not official. - [https://www.scalekit.com/connectors/claricopilot](https://www.scalekit.com/connectors/claricopilot) - [https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980](https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980) **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. API access is self-service inside the product (Workspace Settings) once you are an active Copilot subscriber - no separate sales-gated enable step like the main Clari API. Whether a solo operator can become a Copilot customer at all without a sales call is unknown. **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** - [Draft personalized outreach](../jobs/draft-personalized-outreach.md) - [Fetch a call transcript](../jobs/fetch-call-transcript.md) - [Summarize a meeting](../jobs/summarize-meeting.md) - [Extract deal signals from calls](../jobs/extract-deal-signals-from-calls.md) - [Write CRM records](../jobs/write-crm-records.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.clari.com/products/copilot/](https://www.clari.com/products/copilot/) - [https://api-doc.copilot.clari.com/](https://api-doc.copilot.clari.com/) - [https://community.clari.com/product-q-a-6/how-to-use-copilot-apis-2258](https://community.clari.com/product-q-a-6/how-to-use-copilot-apis-2258) - [https://www.scalekit.com/connectors/claricopilot](https://www.scalekit.com/connectors/claricopilot) - [https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980](https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980) 5 source URLs. Raw sources field, verbatim: https://www.clari.com/products/copilot/, https://api-doc.copilot.clari.com/, https://community.clari.com/product-q-a-6/how-to-use-copilot-apis-2258, https://www.scalekit.com/connectors/claricopilot, https://community.clari.com/product-q-a-6/why-was-copilot-mcp-server-removed-from-the-july-release-notes-2980 **Notes, verbatim from the file** The removed-from-release-notes thread is worth watching - an official Clari Copilot MCP server may land later and should be re-checked. **Provenance** - **Entry id**: 03-clari-copilot - **Source file**: 03-conversation-intel.md - **Source line**: 49 - **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).