Last updated: May 30, 2026
When Anthropic launched Claude for Legal on May 12, it didn’t ship one legal AI — it shipped twelve. Twelve practice-area plugins plus more than 20 connectors to the software firms already run on, all open-source on GitHub, where it pulled close to 900 stars in its first day. The launch buzz answered the question “is Claude good at legal work?” The question it left open is the one that actually matters when you sit down to use it: which of the twelve do I install for the work I actually do?
This is a role-by-role map. No hype, just which plugin fits which desk.
What Anthropic actually shipped
Each plugin is a packaged set of skills, prompts, and guardrails for one slice of legal work, and they’re designed to run inside Claude Cowork. They’re open-source (Apache 2.0), so a firm can fork them, extend them, or run them on its own API key — and lawyers are already doing exactly that. The connectors wire Claude into the tools you already use: DocuSign, Ironclad, iManage, NetDocuments, LexisNexis, Thomson Reuters, Everlaw, Box.
The thing to understand before you install anything: a plugin isn’t magic out of the box. Each one starts with a short setup interview — roughly 10 to 20 minutes where it learns your playbooks, your escalation chain, your risk tolerance, and your house style by reading a few seed documents you point it at (a signed MSA, a prior review memo, a playbook). There’s a 2-minute quick start if you want to be productive first and refine later.
The role-by-role map
Here’s which plugin earns its keep at which desk, based on what each one is built to do.
| Plugin | Best for | What it actually does |
|---|---|---|
| Commercial | In-house counsel, contracts teams | Reviews vendor agreements and NDAs against your playbook, routes escalations, writes a plain-language summary for the business |
| Corporate / M&A | Deal lawyers, corporate generalists | Diligence across the data room, disclosure schedules, board consents, the closing checklist |
| Employment | Employment lawyers, HR-facing counsel | Hires, terminations, worker classification, leave deadlines, investigations; drafts policies with state-specific rules |
| IP | Patent and trademark practitioners | Patent prosecution support, trademark monitoring, licensing drafts, portfolio management |
| Litigation | Litigators, trial teams | Case strategy, brief drafting support, deposition prep, motion checklists, chronology building |
| Privacy | Privacy and data-protection counsel | Privacy reviews, data-handling assessments, policy drafting |
| Regulatory | Compliance and regulatory lawyers | Regulatory monitoring and analysis against your obligations |
| AI Governance | Counsel standing up AI policy | Frameworks and reviews for an organization’s AI use |
| Product | Product counsel | Launch reviews, product-legal sign-offs |
There are also plugins aimed at legal education — law students and clinics — plus a builder track for firms that want to roll their own. The pattern across all of them is the same: they’re best at the repetitive first pass a junior would otherwise do, not the judgment call at the end.
How to install one
You don’t need a developer. The flow is short.
In an enterprise, your admin enables the connectors and plugins in workspace settings; a solo or small firm can add them directly. The setup interview is the step people skip and regret — the five minutes you spend pointing it at your own NDA playbook is what turns generic output into something that sounds like your firm.
Which should you start with?
That last caveat is real and worth repeating. Early benchmarking by lawyers found the litigation tools genuinely good at extracting facts and building a timeline from a case file, but noticeably weaker at the harder reasoning — spotting the issues, assessing the claims, sizing the damages. One tester described it as “jagged”: excellent at one sub-task, mediocre at the next, inside the same job. Treat it as a fast, tireless junior, not a senior associate.
What this can’t do
- It doesn’t replace the lawyer. Every plugin ships with explicit guardrails: outputs are drafts, citations need to be checked against sources, and a human review gate stays in place. You own the final call.
- It’s uneven by task. Strong on extraction and summarizing, weaker on judgment-heavy analysis. Know which side of that line your task is on.
- It needs your playbook to be useful. Skip the setup interview and you get generic output. The customization is the product.
- The pricing isn’t public. You need a Claude plan, and enterprise deployments run on the firm’s own API key — budget the usage, not just a flat license.
- You’re working with material you already own. One fair critique making the rounds: for some tasks you’re paying to have Claude read documents your firm already has. Aim it at the genuinely time-saving work, not everything.
What this means for you
If you’re a solo lawyer: This is the most leverage you’ve ever had on the boring 80% of the work. Install one plugin — the one matching your highest-volume task — do the setup interview properly, and run it on real files for a week before you add a second.
If you’re in-house: The Commercial plugin plus the “summarize this for the business in plain English” habit can change how fast legal turns things around. Start there, measure the time saved, then expand.
If you’re a litigator: Use it for the grunt work — chronologies, document review, depo prep — and keep your own eyes on strategy and damages. The benchmark gap is a feature of where the tech is, not a bug you can prompt away.
If you’re a law student or clinic: There’s a track built for you, and learning these tools now is the cheapest career investment available. The firms you’re applying to are installing them this quarter.
The bottom line
Claude for Legal isn’t one decision — it’s twelve, and the smart move is to make exactly one of them today. Pick the plugin that matches the task you do most, give it your real playbook in the setup interview, and judge it on a week of actual files. It won’t be your senior associate. It’ll be the tireless junior who does the first pass at 2 a.m. so you can spend your day on the work that needs a lawyer.
New to running these tools in a practice? Our AI for Solo Lawyers: Legal Agent Workflow course walks through setting up Claude for Legal without putting client data or privilege at risk.
