Clari

Clari + Salesloft

Clari + Salesloft is included because Salesloft is rolling out an official revenue MCP spanning pipeline and deal context, cadence execution, conversation intelligence, and forecast inspection across AI clients, with some capabilities current and others explicitly phased through late summer 2026.

CRM, revenue & customerSystem of recordExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of record
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Salesloft pipeline movement and progression, deal history and activity, cadence execution and engagement signals; Clari Copilot call topics and keywords; and announced Clari forecast and deal-inspection context.

02 · Data you can retrieve

Use currently listed or phased MCP integrations to inspect revenue execution context, including Salesloft deal and cadence activity, conversation intelligence, and announced Clari forecast or deal data. Availability depends on rollout stage and client.

03 · Actions and write paths

Salesloft announced write-back inside Salesloft and Clari as part of the phased late-summer rollout, but the reviewed first-party announcements do not publish a tool-by-tool write catalog, authentication model, or confirmation behavior.

04 · Authentication and permissions

The reviewed MCP announcements do not specify the MCP authentication flow, scopes, role mapping, or tenant permission inheritance. Do not substitute Clari or Salesloft REST API authentication assumptions for this MCP surface.

05 · Monitoring, approval, and recovery

Salesloft describes phased client and write-back expansion but does not document MCP audit events, per-tool consent, or approval controls in the reviewed announcements. BYO-UI should label rollout status and hold write-back behind explicit review until product documentation defines those controls.

06 · Limits and caveats

The public evidence is announcement-level rather than a technical tool catalog. Claude directory availability is current as of July 9, while Cadence/activity expansion, Clari Copilot data, ChatGPT, write-back, Microsoft/Google connectors, and Clari forecast/deal listings are described on a phased late-summer 2026 schedule.

Agent access

MCP support

Official MCP serverSalesloft-hosted Clari + Salesloft revenue MCP with phased client, data, and write-back expansionClaude-directory integration current; broader Clari + Salesloft data, client, and write-back coverage in phased late-summer 2026 rollout

Support: Official MCP server

Read scope: Current and announced reads cover Salesloft pipeline, deal, cadence, engagement, and conversation context plus phased Clari forecast and deal inspection; exact availability varies by client and rollout date.

Write scope: Write-back inside Salesloft and Clari is announced for phased expansion through late summer 2026; no public MCP tool list or operation-level availability matrix was found. Native cross-product task and email actions should not be presumed to be MCP tools.

Authentication: Not specified in the reviewed first-party MCP announcements.

Approval boundary: No MCP-specific confirmation or write-approval mechanism is described in the reviewed announcements. BYO-UI should require explicit review of destination, record, and proposed change for any released write-back tool.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access3
UI extensibility4
Portability3
Observability3
Documentation2

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Clari ships them.

Single-platform patterns

  • Forecast, pipeline inspection, and seller-action room
  • Account journey room
  • Pipeline-quality debugger
  • Customer expansion cockpit
Use in the brief builder →

Multi-platform compositions

  • Clari + Salesloft + marketing or intent platform: account journey room
  • Clari + Salesloft + conversation or support system + analytics or warehouse: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources
APISource inventory
https://developer.clari.com/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.clari.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.