Claude for Lawyers, in one paragraph: Anthropic's Claude for Legal launched on 12 May 2026 with 12 practice-area plugins and more than 20 connectors to legal software, and both are free to install on any paid Claude plan. A 5 to 50 attorney firm gets the same legal features as the big-name launch customers. The plan you pick decides seats, admin controls and data terms, and the setup decides whether it's safe.
Updated 2 October 2026: plan and data-retention facts rechecked against Anthropic's privacy center, launch details against LawSites' launch coverage. We maintain open-source Claude connectors for Clio and MyCase.
12practice-area plugins at launch, 12 May 2026.
20+connectors to legal software: iManage, Relativity, Ironclad and more.
$0extra to install them on a paid Claude plan.
0Clio or MyCase connectors in the launch list. Those came from elsewhere.
What Claude for Legal actually is
It's a set of add-ons that install into the Claude you already use. The 12 plugins shape how Claude approaches work in an area: commercial, corporate, privacy, product, employment, regulatory, IP, litigation and AI governance, among others. The connectors let Claude reach software firms already run. Per LawSites, the launch list included DocuSign, Ironclad, Definely, iManage, NetDocuments, Box, Everlaw, Relativity, Thomson Reuters' CoCounsel Legal and Harvey.
Read that list again and you'll notice it's built for large firms with document management and e-discovery budgets. The system a 12-attorney firm lives in every day is its practice management tool, and Clio and MyCase weren't on the launch list. MyCase later shipped an official read-only connector for Claude Team and Enterprise. For Clio, and for writing back into either system, there are open-source connectors, including ours for Clio and MyCase.
Which Claude plan fits a small firm?
The plugins work on any paid plan, so the choice comes down to how many people use it, how much admin control you want, and what happens to the data. Our full comparison of Claude plans for law firms goes deeper on usage limits. The short table:
| Plan |
Good for |
Data terms worth knowing |
| Pro or Max |
One lawyer testing it on non-client work |
Consumer plan Consumer terms. Keep client matters out. |
| Team |
Most firms of 5 to 50 for everyday drafting, research and summaries |
Commercial terms No training on your data by default. Chats are kept until deleted, then removed from backend systems within 30 days. |
| Enterprise |
Firms that need SSO, audit logs and central control over connectors |
Commercial terms Same training default, plus admin tooling. Zero data retention doesn't apply to chats in the app. |
| API under the firm's key |
Defined workflows on the most sensitive matters |
ZDR if approved Inputs deleted within 30 days by default. Zero data retention is available to approved organizations; the newest Covered Models need 30-day retention. |
Two facts from Anthropic's privacy center matter most here. It doesn't use inputs or outputs from commercial products, Team, Enterprise and the API among them, to train its models by default. And its zero data retention arrangement applies only to eligible APIs, products using your commercial API key and Claude Code on Enterprise, approved per organization. An earlier version of this post said Enterprise chat had zero retention by default. It doesn't, and we've corrected that.
Where a small firm actually saves time
The demos are drafting and research. The time a 12-attorney firm actually gets back is quieter: Claude reading the matter, the contacts, the deadlines and the documents straight from Clio or MyCase, so nobody copies them into a chat window first. "What's overdue on my open matters this week?" only has an answer if Claude can see the system.
That connection runs over MCP, the open protocol Claude for Legal's connectors use too. With one in place, an associate asks for a draft against the actual file, and Claude can create the follow-up task back in the practice management system once someone approves it. Our connectors log every read and write to an append-only file, which is what a firm needs when someone later asks what the AI touched.
Want Claude set up for the whole firm?
We pick the plan with you, connect it to Clio or MyCase and your documents, write the review policy and train the team. Each attorney signs in as themselves, and there's one log of what the connectors did.
Talk to a founder
The setup checklist for a firm
This is the list we work through when a firm asks us to roll Claude out. Most of it is decisions, not code, and every item has bitten a firm that skipped it.
1
Plan and seats
Team for everyday work, the API for defined workflows on sensitive matters, Enterprise if you need SSO and audit logs. Decide who gets a seat and who shares a workflow instead.
2
Permissions and projects
Projects split by practice group, so the employment team's knowledge base isn't the PI team's. Connectors turned on only where a workflow needs them.
3
Knowledge base
Your templates, precedents, style guide and checklists loaded into projects, so drafts start from the firm's way of doing things.
4
Connectors
Clio or MyCase for matters, Microsoft 365 or your DMS for documents, scoped to what each workflow needs, with a log of every read and write.
5
Plugins and agents
The Claude for Legal plugins that match your practice areas, plus one or two firm-specific workflows, such as intake summaries or demand drafts.
6
Review policy and training
A written rule that a lawyer reviews every output, aligned with ABA Formal Opinion 512, and an hour of training per group on what to use it for and what never to paste in.
That's the scope of our firm-wide Claude deployment. If you only need the connector installed for a few people, guided setup is the smaller version.
Keeping it on the right side of privilege
Two federal courts ruled on AI and privilege in February 2026 and reached opposite results. The lesson from Heppner and Warner is that protection follows confidentiality, counsel's direction and litigation purpose, not the brand of the tool. In practice: commercial plans only for client work, counsel directing the task, a lawyer reviewing every output before it counts, and a record of which matter data went to which vendor. We wrote up both rulings in is it safe for lawyers to use ChatGPT or Claude.
One thing we won't tell you is that nothing leaves the firm. With hosted Claude, prompts are processed by Anthropic or your cloud provider. What you can defend is the plan's terms, the retention you configured, and the review and logging you put around it.
Frequently Asked Questions
What is Claude for Legal?
Claude for Legal is Anthropic's legal release, launched on 12 May 2026. It added 12 practice-area plugins, covering areas such as commercial, corporate, privacy, employment, regulatory, IP and litigation work, and more than 20 MCP connectors to legal software such as iManage, NetDocuments, Ironclad, DocuSign, Relativity, Everlaw, Thomson Reuters CoCounsel Legal and Harvey. The plugins and connectors are free to install for any paid Claude customer.
Do you need an enterprise contract to use Claude for legal work?
No. The plugins and connectors install on any paid Claude plan. What a bigger plan adds is administration: SSO, audit logs, a Compliance API, central controls over connectors. For a firm of 5 to 50 attorneys the usual choice is Team for everyday work, with the API under the firm's own key for defined workflows that touch the most sensitive matters.
Can Claude connect to Clio or MyCase?
Yes. MyCase ships an official read-only connector for Claude Team and Enterprise. Oktopeak maintains open-source connectors for Clio and MyCase that read and write, with an append-only audit log of every action. With a connector, Claude reads matters, contacts, documents and calendars directly instead of staff pasting them into a chat.
Is Claude safe for privileged client data?
It can be used responsibly, and the setup decides that. Anthropic doesn't train on commercial plans by default. Zero data retention is available only for eligible API use and Claude Code on Enterprise, approved per organization, and doesn't cover chats in the Claude app. After the February 2026 Heppner and Warner rulings, the defensible posture is a commercial plan, counsel directing the work, a lawyer reviewing every output, and a record of what was sent where.
What does a firm need to set up before rolling Claude out?
A plan matched to how the firm will use it, sign-in and seat rules, projects split by practice group, a knowledge base of the firm's own templates and precedents, connectors to the practice management system and documents, a written review policy aligned with ABA Formal Opinion 512, a log of what connectors read and wrote, and training for attorneys and staff.
Next step
If you want Claude working inside your practice, connected to the system your matters live in and set up so you can defend it, book 30 minutes with us. We'll tell you which plan fits, what to connect first, and what to leave off.