Claude for Legal

A curated summary of the latest Anthropic product release targeting the legal community

Legal teams at the precipice of transformation

Open-source capability add-ons for Claude Cowork that set the stage for creative disruption across legal teams.

On May 12, 2026, Anthropic shipped the “Claude for Legal” marketplace plugins covering a wide array of legal practice disciplines and workflows. The updated marketplace also includes more than 20 MCP connectors linking Claude to various legal tech platforms (Ironclad, iManage, NetDocuments, CoCounsel, Westlaw, Datasite, Box, etc.) and pre-built agents related to recurring tasks for the corresponding plugins.

These aren't products to license. As with all Anthropic-published plugins and skills, these are available for free via GitHub. The plugins are open source and can be cloned and edited (skillfully) by users. Each plugin contains a ‘setup interview’ skill that captures the user org's playbook, escalation chain, risk calibration, and house style. This type of product is closer to a package manager than a SaaS vendor – install, inspect, customize, or remove.

What this analysis covers

  • Plugin architecture how a plugin loads, where skills, connectors, commands, and scheduled agents fit.
  • An examination of four curated plugins with direct applicability to identified use cases.
    • ~40 skills, 6 agents, 20+ connectors
  • Strategy considerations – near & long-term potential, and open considerations that will dictate viability for your org.

Plugins have five key elements

A consistent set of components makes it easy to scale-out plugins and stack workflows.

1

Interview

10–15 min conversational onboarding writes a natural language practice profile that captures playbook, jurisdiction, risk posture, and escalation rules. No coding required.

2

Skills

Each skill is a structured workflow: review a contract, triage an NDA, build a chronology. Skills reads the profile first, apply the playbook, and produce work produced ready for attorney review.

3

Commands

Pre-defined slash commands allow explicit invocation of skills in Claude Cowork or Claude Code. Application-wrapped workflows, scripts, and agents can leverage these commands for unambiguous invocation.

4

Connectors

Pre-wired MCPs for tools like Ironclad, DocuSign, CourtListener, Slack, and Google Drive. Different use cases and workflows are enabled depending on the connected platform, but connecting to other platforms is purely optional for many use cases (necessary for others).

5

Agents

Background tasks watch for changes and updates, even when nobody is looking: renewals coming due, dockets with new filings, leaves nearing deadlines, deviations worth a playbook update.

Build-path read

The practice profile, skills, MCP connectors, and agents are the same primitives we'd use to author our own custom workflows in 2027.

Commercial task automations

Powerful automations for common transactional tasks related to legal review of commercial activity.

What it does
  • Reads inbound vendor MSAs, NDAs, and SaaS subscriptions and produces a deviation-by-deviation memo against our playbook with specific redline language.
  • Triages NDAs into GREEN / YELLOW / RED so non-lawyers can self-serve the routine ones and legal sees only what needs eyes.
  • Routes any issue that exceeds the reviewer's authority through the right approver, drafts the ask, and tracks the response.
  • Traces amendment history: what changed across base + amendments, or where a specific clause now lives after edits over time.
  • Translates a legal review into a two-paragraph stakeholder summary for procurement, sales, or the business owner.
Key skills
  • vendor-agreement-review: full playbook deviation analysis
  • nda-review: fast GREEN / YELLOW / RED triage
  • saas-msa-review: auto-renewal, data exit, SLA focus
  • renewal-tracker: cancel-by deadlines, 90-day horizon
  • escalation-flagger: matches matrix, drafts approver ask
  • amendment-history: trace changes across versions
  • stakeholder-summary: business-readable rollup
Runs on schedule

renewal-watcher (weekly Mon) · deal-debrief (weekly Mon) · playbook-monitor (data-triggered, proposes updates after 5 deviations on one clause in 12 months)

Connectors out of the box

Ironclad (CLM) · DocuSign (envelope status) · Slack · Google Drive

Intellectual Property analysis

Brand, content, invention portfolio protection that defends the company's intangible assets.

What it does
  • Reviews IP clauses in inbound MSAs, SOWs, licenses, and contractor agreements: assignment language, license grants, IP indemnity, OSS reps.
  • Triages incoming infringement situations (knockoffs, copycats, suspected lifting) into ignore / soft letter / C&D / file with factors cutting each way.
  • Drafts and triages DMCA takedowns and §512(g) counter-notices, gated on the fair-use and perjury checks before anything goes out.
  • Runs first-pass trademark clearance and freedom-to-operate triage: flag lists for attorney review, never a go/no-go.
  • Checks open-source license compliance on a dependency list or repo: copyleft obligations, attribution, license compatibility.
  • Maintains a portfolio register and surfaces upcoming renewal, affidavit, and maintenance deadlines.
Key skills
  • ip-clause-review: assignment, license, indemnity, OSS reps
  • infringement-triage: TM, copyright, patent, trade secret
  • takedown: DMCA send, receive, or counter-notice
  • cease-desist: send mode or inbound triage
  • clearance: knockout + confusion factors first pass
  • fto-triage: blocking-patent flag list
  • oss-review: license compliance check on code
  • portfolio: registrations, renewals, deadlines
Runs on schedule

ip-renewal-watcher (weekly): computes what's due in the next 90 days across registrations, affidavits, and maintenance filings

Connectors out of the box

Solve Intelligence (patent / non-patent literature) · CourtListener · Descrybe (primary-law research) · Slack · Google Drive

Litigation management

Keeping in-house counsel in control and aligned with litigation requirements, deadlines, and outside counsel activities.

What it does
  • Stands up a uniform matter intake (risk triage, materiality, conflicts, outside counsel, owners, legal hold, key dates) and writes a structured matter file plus a portfolio log entry.
  • Rolls up the portfolio on demand: risk distribution, upcoming deadlines, stale matters, materiality totals, flagged anomalies.
  • Issues, refreshes, releases, and reports on legal holds; drafts the notice as .docx and updates the log.
  • Triages incoming demand letters and subpoenas into options memos with portfolio cross-check, objections framework, and a compliance plan.
  • Drafts demand letters from intake, gated on a FRE 408 / privilege / waiver checklist, with a post-send checklist.
  • Builds chronologies from declared document sources, tagged by significance per matter theory. Generates weekly OC status-request email drafts across the portfolio.
Key skills
  • matter-intake / matter-update / matter-close
  • portfolio-status: risk, deadlines, staleness rollup
  • matter-briefing: pre-call deep read on one matter
  • legal-hold: issue / refresh / release / status
  • subpoena-triage: scope, burden, privilege, plan
  • demand workflows: intake, draft (FRE 408 gated), inbound triage
  • chronology: significance-tagged timeline
  • oc-status: weekly OC status email drafter
  • claim-chart: element-by-element with gap detection
Runs on schedule

docket-watcher (weekly): pulls new filings for matters in the portfolio, computes candidate deadlines, cross-references each matter's history

Connectors out of the box

CourtListener (opinions, PACER) · Trellis (state trial courts) · Everlaw / Aurora (eDiscovery) · Slack · Google Drive

Employment law toolkit

From hire to exit, plus the policy and investigations work that keeps the people function defensible.

What it does
  • Reviews offer letters and restrictive covenants with jurisdiction-specific rules researched and cited at the time of review, not stored from a stale table.
  • Walks a termination scenario through high-risk flags, severance/release framing, and final-pay timing by state.
  • Drafts policies with state supplements baked in across our jurisdictional footprint; diffs proposed handbook changes against current language to surface ripple effects.
  • Opens and manages a privileged internal investigation workspace: intake, sources checklist, investigation log, audience-specific memo summaries.
  • Tracks open employee leaves with hard legal deadlines (FMLA, state equivalents, USERRA, ADA-as-accommodation) and fires decision-point alerts before deadlines pass.
  • Kicks off international expansion planning for a new country: EOR vs. entity framing, cross-functional triggers, outside-counsel briefing requests.
Key skills
  • hiring-review: offer + restrictive covenants
  • termination-review: risk flags + severance + final pay
  • policy-drafting: with state supplements
  • handbook-updates: diff + ripple-effect flagging
  • wage-hour-qa: jurisdiction-aware, cite-on-demand
  • worker-classification: IC / employee / vendor
  • investigation-open / add / query / memo / summary
  • leave-tracker / log-leave
  • expansion-kickoff / expansion-update
Runs on schedule

leave-tracker (weekly Mon): surfaces only the leaves where a decision is required and explains why; not a status board

Connectors out of the box

Slack · Google Drive (plus research tools the session has access to for jurisdiction-specific rules)

Full-picture summary

What we've covered, what we didn't, and where this may head.

Near term
  • The marketplace is a useful proving ground for custom AI-backed legal workflow automations.
  • In-house teams with predictable scopes of work and definable runbooks are particularly well-positioned to leverage tools like this.
  • The marginal cost for Claude Enterprise subscribers = time to configure and experiment.
  • Cowork users can immediately leverage Claude + plugins for day-to-day work.
  • SaaS vendor upsides not covered by plugins: support contracts, polished UI/UX, granular permissions/access, and limited risk outsourcing.
Open questions
  • Legal Ops teams own and manage tools own tools; Claude plugins are no different.
  • The marketplace currently has twelve plugins, not four. Operators and practitioners are best suited to identify how and where workflow optimization occurs.
  • Plugins are living resources that can be upgraded and customized but need some level of administration.
  • Interviews and corresponding runbooks are fully-owned assets that require SME maintenance.
  • Out-of-the-box platform integration and tool-calling capabilities are not guaranteed for any given commercial platform.
Long term
  • Orgs with in-house development teams can wrap custom applications around these capabilities.
  • API calls, skills, custom connectors with tools, and code execution that emulates plugin behavior, including runbooks.
  • Many commercial SaaS tools leverage the same underlying AI models as Cowork – the underlying “brains” are not proprietary.
  • Legal Builder Hub is a separate plugin that finds and installs community-built legal skills – this is another area of opportunity (and risk).
Bottom line

Claude for Legal (May 2026) is a useful starting point, not the end game. The marketplace will keep growing, and so will legal teams' ability to embed AI.