Claude + Litify: What the Integration Can (and Can't) Do in 2026
Partly — there’s no dedicated Claude-Litify connector, but because Litify is built natively on the Salesforce platform, you can reach Litify’s data through Salesforce’s official Hosted MCP Servers. Litify stores everything — Matters, Intakes, Negotiations, settlements, time entries — as Salesforce custom objects (60+ of them in the managed package). Salesforce’s hosted sObject MCP server connects Claude to your org over OAuth 2.0 and lets it run SOQL queries, modify records, and trigger Apex actions and Flows, all bounded by the running user’s Salesforce permissions. So Claude can read and even write Litify records — but Litify itself ships no Claude connector, it was not among the 20+ integrations in Anthropic’s May 2026 Claude for Legal launch, and everything happens inside a Claude session you’re driving — nothing watches your matters between chats.
Here’s what the Salesforce path actually does, how to turn it on, where the ceiling is, and what to use if you want Litify-adjacent work that runs on its own.
What Claude can actually do with Litify
There’s no Litify-branded connector in Anthropic’s directory, and Litify wasn’t one of the case-management or document platforms named in Claude for Legal (that list leaned toward iManage, NetDocuments, Box, Relativity, Everlaw, and Thomson Reuters). The working route is Salesforce’s own hosted MCP server, because Litify data is Salesforce data.
Through Salesforce Hosted MCP Servers connected to Claude Desktop or Claude Code:
- Query Litify records in natural language. Because Litify’s Matters, Intakes, and related records are Salesforce custom objects (the
litify_pm__andlitify_qa__namespaces), Claude can run SOQL against them — “list open Matters in litigation with no activity in 30 days,” “show settlement amounts on Matters that closed last quarter” — and cite the records it read. - Modify records and execute actions. The Salesforce Developers walkthrough shows Claude running SOQL queries, modifying records, and invoking Flows and Apex methods. Applied to Litify, that means updating a Matter’s stage, editing a field, or firing a Litify Flow — subject to what the connected user can do.
- Respect Salesforce permissions. Standard Salesforce user access permissions apply on top of the app-level access checks, so Claude only ever touches records the authenticating user could touch in Litify.
- Draft the surrounding work. Once Claude has the matter context, it can draft a client update, a status memo, or a demand-letter outline in the same conversation.
The important nuance: this is Salesforce’s connector reaching Salesforce objects. Litify runs on that data model, so it comes along for free — but no part of it is Litify-specific tooling, and whether a given managed-package object is reachable depends on your org’s configuration and the running user’s object/field permissions.
How to set it up
This is a Salesforce-admin plus paid-Claude-plan flow, not a one-click connector:
- In your Salesforce org, enable Hosted MCP Servers and create an External Client App for OAuth. Copy the consumer key.
- In Claude Desktop or Claude Code, add a custom MCP connector pointing at your org’s hosted MCP server URL (custom connectors require a paid Claude plan). Paste the consumer key as the OAuth Client ID and pick the production vs. sandbox endpoint.
- Complete the OAuth 2.0 redirect flow; Salesforce issues an access token back to Claude for subsequent requests.
- Test with something read-only first — “how many open Litify Matters do I own?” — before letting Claude write anything back.
There is no Litify-side setup because there’s no Litify connector; you’re authorizing Claude into the Salesforce org that Litify lives in.
The limits that matter
Even fully wired, the shape is “a session you drive,” not “an assistant that runs.” Four limits define it:
- No triggers, ever. MCP tools only run inside a conversation you start. Nothing fires when a new Intake lands, a statute-of-limitations date approaches, or a Matter stalls. You have to be there, prompting — Claude won’t watch your caseload.
- Session-bound and permission-scoped. Every query and edit needs a live session and is bounded by the connected user’s Salesforce permissions. There’s no standing process, and no service acting on the firm’s behalf between chats.
- Laptop-bound. Even Claude Cowork’s scheduled tasks run on a fixed clock, not on inbox events. Close the lid and nothing happens.
- Draft-only email. Claude’s Gmail integration drafts messages but doesn’t send them. So even when Claude pulls a Matter and writes the client update, a human still has to hit send — the follow-through stops at the draft.
So Claude is genuinely useful for “pull this matter and help me write the update right now,” and not built for “watch our Litify caseload and act when something changes.”
If you want Litify-adjacent work that runs on its own: Carly
The moment you want something to happen around Litify without you in the chat — a new intake acknowledged and routed within minutes, a reminder when a Matter has gone quiet, a Monday caseload digest built and sent, a settlement update posted to the right Slack channel — you’ve crossed past what a session-bound MCP connector is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a session:
- Fires on events and schedules, 24/7, in the cloud. When a Matter changes stage or a new intake is created in Litify, Carly reacts — summarizes it, emails the client, updates the record, posts to Slack — while your laptop is closed.
- Litify is a native Carly integration. Carly reads and writes Litify records — update a Matter, log activity, create a task — not just surface them in a chat.
- Sends, not just drafts. Carly drafts and sends email across Gmail and Outlook, books meetings, manages tasks, and records meetings — the follow-through that stops at the draft with Claude.
- Builds the workflow by interviewing you. Tell Carly “when a Matter moves to Litigation, draft a status email to the client and create a follow-up task” in plain English; it interviews you and builds it — no External Client App, no SOQL, no prompt engineering.
Carly connects to 200+ tools across 40+ categories natively — see integrations. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude (via Salesforce MCP) | Carly | |
|---|---|---|
| Query Litify records | Yes (SOQL, session) | Yes |
| Update / create Litify records | Yes (permission-scoped) | Yes, natively |
| Litify-specific setup | None — auth into Salesforce org | Native integration |
| Acts on Litify triggers / events | No | Yes |
| New-intake routing, on the spot | No | Yes |
| Monday caseload digest, on schedule | No | Yes |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Works while laptop is closed | No (session / Cowork laptop-bound) | Yes (cloud, 24/7) |
| Setup | External Client App + OAuth + custom MCP connector (paid plan) | Describe it in plain English |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude reaching Litify through Salesforce’s MCP server is a powerful way to query and edit matters in a chat you’re driving. Carly is a teammate that acts on Litify events as they land.
Frequently Asked Questions
Does Claude work with Litify?
Not through a dedicated connector — Litify ships no Claude integration and wasn’t part of Anthropic’s Claude for Legal launch. But because Litify is built natively on Salesforce, you can reach its records through Salesforce’s official Hosted MCP Servers: connect Claude to your org over OAuth and it can run SOQL and modify records — Litify’s Matters and Intakes included — scoped to the connected user’s permissions.
Is there a Litify MCP server?
There’s no Litify-branded MCP server. The working path is Salesforce’s hosted sObject MCP server, which exposes the Salesforce data model that Litify’s 60+ custom objects live in. So you’re not connecting to Litify directly — you’re connecting Claude to the Salesforce org where Litify’s data is stored.
Can Claude update a Matter in Litify automatically when something changes?
No. MCP tools respond inside a conversation you start — there are no event triggers, so Claude won’t notice a new intake, a stalled Matter, or an approaching deadline on its own. For trigger-based work — “when a Matter moves to Litigation, email the client and create a task” — you need an agent platform like Carly, which integrates natively with Litify and runs in the cloud around the clock.
How do I connect Claude to Litify?
Enable Salesforce Hosted MCP Servers in the org that runs Litify, create an External Client App for OAuth, then add a custom MCP connector in Claude Desktop or Claude Code (a paid Claude plan is required for custom connectors) using the consumer key and your org’s server URL. Complete the OAuth flow, then test with a read-only SOQL query before allowing writes.
More: Claude connectors · Claude + Salesforce · Can Claude send emails · Claude vs Carly · Best AI CRM tools
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."
