Claude + Clari: What the Integration Can (and Can't) Do in 2026
Unlike most tools in this space, Clari actually ships an official MCP server — and it’s already native in Claude’s connector directory. After Clari and Salesloft merged in early 2026, the combined company launched a Clari + Salesloft MCP server (April 2026) and got the Salesloft connector listed natively in Claude’s directory (July 2026). The catch: it’s read-only, it started as Salesloft execution data, and the full Clari forecasting and Copilot layer is still rolling out over MCP through late summer 2026.
Here’s each route, when to pick it, what’s actually live today, and what to use when you want Clari work that happens without you at the keyboard.
Route 1: The native Clari + Salesloft connector in Claude’s directory
This is the easiest path and, for most people, the right one. As of July 2026, Salesloft — now part of the Clari + Salesloft platform — is listed natively in Claude’s connector directory with no custom config. You enable it from Claude’s settings, authorize with read-only OAuth, and then ask questions in plain English across your revenue data alongside your other connected tools.
What’s live now leans toward Salesloft execution data: accounts, people, opportunities, cadences, calls, and activity. Clari’s own forecasting and deal-inspection data, plus Clari Copilot call intelligence, are being exposed through the same MCP layer as part of a phased summer-2026 expansion — so depending on when you read this, the forecasting signals may or may not be flowing yet. It’s worth checking the connector’s current scope in your Claude settings rather than assuming everything is on.
Because it authenticates read-only, this connector answers questions — it does not push updates back into Clari. Write-back was announced as part of the same roadmap but is not the default behavior of the read-only OAuth connector.
Route 2: The Clari + Salesloft MCP server for other clients
If you’re not in Claude’s consumer app — you’re wiring up Claude Desktop, Claude Code, or a custom agent — the underlying Clari + Salesloft MCP server is the same data layer the directory connector sits on top of. It’s a remote MCP endpoint designed to open live revenue data to any MCP-capable client (Anthropic’s Claude, plus ChatGPT, Microsoft Copilot, Gemini, and Salesforce Agentforce were all named at launch).
There are also third-party hosted MCP connectors that wrap the same Clari/Salesloft data (services like clariBI and Scalekit publish read-only Clari Copilot / Salesloft connectors). These can be useful if you want a managed endpoint with its own auth handling, but you’re trusting a middleman with your revenue data — vet them the way you’d vet any data processor. For most teams the official connector is the safer default.
Route 3: Clari’s REST + Copilot APIs directly
When you need something the MCP server doesn’t expose yet — a custom pull of forecast history, a scheduled export, or writing data back — you drop to Clari’s APIs and let Claude (via Claude Code or your own script) call them.
Clari runs a few distinct APIs, and the auth differs by product:
- Clari REST API — base
https://api.clari.com/v2, authenticated with anapikeyheader; partner/ingest endpoints also require apartnerkey. Default rate limits sit around 10 requests/second and 100k/week. Docs live at developer.clari.com. - Clari Copilot API — separate service, authenticated with
X-Api-KeyandX-Api-Passwordheaders (you find both under workspace settings → integrations → Clari Copilot API). Docs at api-doc.copilot.clari.com.
The honest caveat: Clari is an enterprise platform, and API access is gated. Keys typically require the right plan tier and admin provisioning, and partner ingest APIs are partner-gated. This isn’t a paste-your-key-in-five-minutes SaaS — expect to loop in your Clari admin.
The limits that actually matter
- The official connector is read-only. Great for asking about pipeline, deals, and forecast; it won’t update Clari for you. Write-back is roadmap, not default.
- Forecasting and Copilot data are still rolling out. The connector launched on Salesloft execution data; Clari’s forecast, deal-inspection, and call-intelligence layers are arriving through late summer 2026. Verify current scope.
- No triggers. Every one of these routes runs inside a chat session you start. Nothing fires when a deal slips or a forecast call wraps — Claude only looks when you ask.
- Laptop-bound for anything scheduled. A Claude Desktop or Claude Code MCP setup only works while that machine is on and that session is open. Close the lid and the “automation” stops.
- claude.ai on the web can’t reach local/desktop-only setups. The directory connector is the exception (it’s hosted); anything you wired locally isn’t reachable from the web app.
Claude + Clari is excellent for interrogating your revenue picture on demand. It’s not built for RevOps work that has to happen the moment something changes in the pipeline.
If you want Clari work that runs on its own: Carly
Carly is an AI executive assistant built to run on triggers and schedules — no session to babysit. Where Claude answers when asked, Carly acts when something happens.
- When a deal slips to a later quarter in Clari, Carly drafts a deal-risk summary and emails the AE and their manager, then logs it to your tracker.
- When the weekly forecast roll-up updates, Carly pulls the latest numbers every Friday afternoon and sends leadership a plain-English summary — commit vs. best-case vs. plan — before the Monday call.
- When Clari Copilot flags a competitor mention on a call, Carly notifies the deal team in Slack and appends it to a competitive-intel doc.
Carly reaches Clari through your own Clari API key (paste it on the integrations page) — one of 200+ native integrations plus anything with an API via BYO-key. Since Clari’s API is admin-gated, you’ll pull the key from your workspace once; after that Carly runs against it on your triggers.
- No-code setup. You don’t build a workflow diagram — Carly interviews you about what you want to watch and what should happen, then wires it.
- Actually sends. Carly composes and sends real email through Gmail and Outlook, not just drafts.
- Connects to anything. 200+ native integrations, plus any tool with an API through your own key — so the same rule can touch Clari, Slack, your CRM, and email in one flow.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Capability | Claude + Clari | Carly + Clari |
|---|---|---|
| Read & search Clari data | Yes (read-only connector) | Yes (via your API key) |
| Act inside a chat session | Yes | N/A — runs unattended |
| Acts on triggers / schedules | No | Yes |
| Works while your laptop is closed | Directory connector only | Yes |
| Writes back / takes action in tools | Read-only today | Yes |
| Sends email | No | Yes (Gmail + Outlook) |
| Setup | Native connector or MCP config | No-code, Carly interviews you |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best way to ask your Clari data questions; Carly is the way to act on it the second the pipeline moves.
Frequently Asked Questions
Does Claude work with Clari?
Yes. The Clari + Salesloft platform is native in Claude’s connector directory (read-only OAuth) and also ships an official MCP server for other clients. Today it leans on Salesloft execution data, with Clari forecasting and Copilot intelligence rolling out over MCP through late summer 2026.
Is there an official Clari MCP server?
Yes — Clari + Salesloft launched an official MCP server in April 2026, and the Salesloft connector went native in Claude’s directory in July 2026. It’s read-only. That’s unusual for this category; most tools have only community servers or none.
Can claude.ai on the web access Clari?
Through the native directory connector, yes — it’s hosted, so the web app can use it after you authorize. Anything you wired locally (Claude Desktop, Claude Code, a self-hosted MCP endpoint) is not reachable from claude.ai on the web.
Can Claude update a forecast or push data back to Clari automatically?
No. The official connector is read-only, so it answers questions but doesn’t write to Clari, and none of these routes fire on their own — they run only inside a session you start. For triggered, write-capable RevOps work, that’s what a tool like Carly is for.
More: Claude connectors explained · Claude vs Carly · Claude + Gong integration · Best AI CRM tools · Can Claude send emails?
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
