Claude + Salesloft
Salesloft and Clari now share one MCP server. Connect Claude and the cadence activity, the call transcripts, and the forecast become one conversation.
- Category
- Sales Engagement
- Connect via
- MCP · API
- Data
- Read (cadences, activity, calls, forecast) + write-back (gated)
- Stage
- Engage & Convert
- Best for
- Sales teams on Salesloft (and Clari) who want engagement, calls, and forecast data reasoned over together
Salesloft, and why connect it to Claude
Salesloft is the cadence and dialer platform a large share of mid-market and enterprise sales teams run their day on, and since the Clari combination it also carries call intelligence (Clari Copilot) and forecasting. That makes it unusual: the same platform holds what reps did, what customers said, and what the deal is worth.
Connecting Claude lets you reason across those three at once. Which accounts in a stalled cadence had a call where budget came up? Draft the re-engagement step from that call. Which committed deals have no activity in ten days? Write the manager's Monday note. The data was always there; Claude is the part that reads all of it in one pass.
Three ways to wire Claude to Salesloft
Three ways to wire Claude to Salesloft. The connector covers most of it, and the API covers the scheduled version.
The Salesloft MCP server, as a connector
Salesloft launched its official MCP server in April 2026 and added a native listing in the Claude connector directory in July 2026, so it is a search-and-connect setup with no config file. It exposes cadence and activity data, Clari Copilot call intelligence, and Clari forecast and deal inspection data, with write-back so Claude can act inside the platform. Access is tied to Salesloft's agentic add-on, so confirm entitlement with your admin or account team.
The REST API, via Claude Code or the Agent SDK
For recurring jobs, the Salesloft v2 API from Claude Code or the Agent SDK is the shape: a Monday pipeline digest that joins cadence activity to forecast category, a nightly pass that flags people who replied but never got a follow-up, a weekly cadence performance review with rewrite suggestions.
Clay as the bridge
If your outbound lists are built in Clay, keep Claude as the reasoning step in the table and push qualified rows into Salesloft cadences through Clay's integration. Good when the list is the hard part and the cadence is already tuned.
See every GTM MCP server Claude can connect to →
Read first, write on purposeReads across cadences, calls, and forecast are low risk and worth allowing freely. Write-back means Claude can add people to cadences, log activity, or change records inside Salesloft, and each of those is a decision someone owns. Gate them behind approval until the pattern has run clean for a few weeks.
What you can do once they're connected
One question across three datasets: cadence activity, what was said on calls, and where the deal sits in the forecast.
Cadence steps rewritten from the account's real call history instead of the persona template.
A Monday pipeline note for the manager: committed deals with no activity, replies with no follow-up, the calls worth listening to.
Cadence performance read-outs in plain language, with the step to rewrite named.
What to build with Salesloft and Claude
Each is a full playbook or skill you can ship, wired to Salesloft.
Email sequence writer
Draft the cadence steps Claude can then create in Salesloft for approval.
B2B cold email templates skill
The reusable skill behind consistent cadence copy.
Post-call follow-up + CRM note
Turn a Clari Copilot transcript into the follow-up and the note, minutes after the call.
Recurring GTM work with Claude Routines
Schedule the Monday pipeline digest and the weekly cadence review.
Connect it, step by step
- Confirm with your Salesloft admin that your org has the agentic add-on that includes MCP access.
- In the Claude app, open Settings, then Connectors, search for Salesloft, and connect with your Salesloft login.
- Start with a read-only question that joins two datasets, like committed deals with no cadence activity this week, and check it against Salesloft.
- Draft one cadence step from a real call transcript and compare it to what a rep would have sent.
- Move recurring work to Claude Code or the Agent SDK on the v2 API, and keep every write-back behind a review step.
Gotchas worth knowing first
- MCP access is gated by entitlement. If the connector shows up but returns nothing useful, it is usually the add-on, not the setup.
- The Clari data is only as good as the forecast hygiene behind it. Claude will faithfully reason over a commit category nobody updates.
- Call transcripts mangle names and product terms. Give Claude a glossary in the Project or system prompt.
- Write-back is powerful and boring to undo. Adding forty people to a cadence from a bad filter is a real morning of cleanup, so gate it.
Claude + Salesloft: common questions
Does Claude integrate with Salesloft?
Yes. Salesloft runs an official MCP server, launched in April 2026, and it is natively listed in the Claude connector directory as of July 2026. Connect it from Settings, then Connectors, or reach the Salesloft v2 API from Claude Code or the Agent SDK.
What data does the Salesloft connector expose?
Cadence and activity data, Clari Copilot conversation intelligence like topics and keywords from calls, and Clari forecast and deal inspection data, plus write-back so Claude can take actions inside Salesloft and Clari.
Is there a plan requirement?
Access runs through Salesloft's agentic add-on. Check with your admin or account team before building around it, because a connector that connects but returns nothing is almost always an entitlement issue.
Can Claude add people to a cadence?
With write-back, yes, and you should approve it. The pattern that works is Claude proposing the people, the cadence, and the first-step copy, and a human confirming. Bulk enrollments from a wrong filter are tedious to unwind.
What is the first play to run?
The Monday pipeline note: committed deals with no activity, replies without a follow-up, and the calls worth a listen. It uses all three datasets, it is read-only, and managers feel the value in the first week.