Tutorial 06: The Claude Legal Plugin
Master Claude's dedicated Legal Plugin with slash commands for contract review, legal research planning, clause comparison, and compliance checking.
Learning Objectives
By the end of this tutorial, you will:
- Understand and use the Claude Legal Plugin effectively
- Master the
/review-contract,/triage-nda, and other commands - Configure your organization's playbook for the plugin
- Compare plugin functionality to Harvey and Legora equivalents
Part 1: Claude Legal Plugin Overview
What Is the Legal Plugin?
Released February 2026, the Claude Legal Plugin is Anthropic's first domain-specific plugin for Cowork. It provides:
- Pre-built commands for common legal workflows
- Configurable playbook integration
- Risk-flagging with color-coded assessments
- Redline suggestions with specific language
- MCP integration for document management connections
How It Compares to Competitors
| Feature | Claude Legal Plugin | Harvey | Legora |
|---|---|---|---|
| Contract Review | /review-contract | Workflow | Tabular Review |
| NDA Triage | /triage-nda | Yes | Yes |
| Custom Playbook | Full control | Limited | Moderate |
| Risk Ratings | RED/YELLOW/GREEN | Yes | Yes |
| Redline Suggestions | Yes | Yes | Yes |
| Bulk Processing | Coming | 10,000 docs | 100s docs |
Requirements
What You Need
- Claude Pro, Max, Team, or Enterprise subscription
- Claude Desktop app (macOS) for Cowork
- Optional: Configured playbook file
Pricing is set by Anthropic and may change. Verify current pricing on the official Claude site.
Part 2: Plugin Commands Reference
/review-contract - Clause-by-Clause Contract Review
Purpose: Comprehensive contract analysis against your playbook
Syntax:
What It Does:
- Identifies contract type and parties
- Analyzes each material clause
- Compares to your configured playbook positions
- Assigns risk ratings (GREEN/YELLOW/RED)
- Provides specific redline suggestions
- Generates negotiation priority list
Example Output:
/triage-nda - Rapid NDA Pre-Screening
Purpose: Quickly categorize incoming NDAs for appropriate handling
Syntax:
What It Does:
- Identifies NDA type (mutual/one-way, direction)
- Scans for non-standard or problematic terms
- Categorizes into handling tracks
- Provides specific concerns if not standard-track
Triage Categories:
| Category | Description | Action |
|---|---|---|
| GREEN - STANDARD APPROVAL | Matches our standard or better | Paralegal can execute |
| YELLOW - COUNSEL REVIEW | Minor deviations | Attorney quick review |
| RED - FULL REVIEW | Significant issues | Full legal analysis |
Example Output:
Time Savings
Processing 15 NDAs: ~2 hours with triage vs 6+ hours manually. Standard-track NDAs can be routed directly to a paralegal for execution.
/vendor-check - Vendor Agreement Status
Purpose: Check status of agreements with known vendors
Syntax:
Requires MCP
This command requires an MCP connection to your document management system.
Example:
/brief - Generate Contextual Briefings
Purpose: Create briefing documents for various needs
Syntax:
Brief Types:
daily- Daily brief on pending matterstopic- Research brief on specific topicincident- Incident response brief
Example:
/respond - Templated Legal Responses
Purpose: Generate standard responses for common requests
Syntax:
Request Types:
dsar- Data Subject Access Request responsedeletion- Data deletion request responsehold- Litigation hold noticesubpoena- Subpoena acknowledgment
Example:
Part 3: Configuring Your Playbook
Configuration File Location
The Legal Plugin checks for a playbook configuration in:
Configuration Structure
Setting Up Your Configuration
Step 1: Create the config file
Step 2: Copy and customize the template above
Step 3: Test with a sample contract
Step 4: Refine based on output
Customize for Your Needs
The playbook drives all risk assessments and redline suggestions. Generic playbooks will produce generic results. Invest time customizing positions for your organization's risk tolerance and standard negotiation positions.
Part 4: MCP Integrations for Legal Plugin
Available Integrations
The Legal Plugin can connect to external tools via MCP:
| Integration | Purpose | Setup Complexity |
|---|---|---|
| iManage | Document management | Moderate |
| NetDocuments | Document management | Moderate |
| SharePoint | Document storage | Low |
| Clio | Practice management | Low |
| Midpage | Legal research | Low |
| Slack | Notifications | Low |
Example: Connecting Midpage for Legal Research
The Midpage MCP integration provides case law access directly within Claude.
Requirements:
- Midpage subscription
- Claude Pro/Team/Enterprise
Setup:
- Get Midpage API credentials
- Configure in Claude Desktop MCP settings
- Use legal research within plugin workflows
Usage Example:
Part 5: Workflow Examples
Workflow 1: End-to-End Contract Review
Workflow 2: NDA Volume Processing
Workflow 3: Incident Response
Part 6: Best Practices
Do's
- Do configure your playbook before heavy use
- Do verify all citations and legal conclusions
- Do use Projects for matter separation
- Do review RED items carefully before accepting suggestions
- Do customize templates for your jurisdiction
Don'ts
- Don't rely solely on plugin output for legal decisions
- Don't skip verification of case citations
- Don't use generic playbook for specialized matters
- Don't share plugin output with clients without review
- Don't assume plugin catches everything
Professional Judgment Required
The Legal Plugin is a powerful efficiency tool, but it is not a replacement for attorney judgment. Always verify critical recommendations, especially RED-flagged items and suggested redlines.
Quality Control Checklist
For every plugin-assisted review:
- Verified contract type identification is correct
- Confirmed our role (customer/vendor) is correct
- Checked each RED item manually
- Verified suggested language is appropriate
- Confirmed jurisdiction-specific requirements
- Reviewed for issues plugin may have missed
- Applied professional judgment to recommendations
Practice Exercises
- Set up your playbook configuration file with your organization's standard positions
- Run
/review-contracton 3 different contract types and compare results - Run
/triage-ndaon 5 NDAs and compare to your manual triage - Test one MCP integration (Midpage or document management)
- Create a workflow checklist for your most common task
Command Quick Reference
| Command | Purpose | When to Use |
|---|---|---|
/review-contract | Full contract analysis | New contracts, renewals |
/triage-nda | Quick NDA categorization | High-volume NDA processing |
/vendor-check | Vendor agreement status | Renewal prep, due diligence |
/brief daily | Daily matter summary | Morning briefings |
/brief topic | Topic research | New legal issues |
/brief incident | Incident response | Breaches, litigation |
/respond dsar | Privacy request response | GDPR/CCPA requests |
/respond hold | Litigation hold | New litigation matters |
Next Steps
Continue to Tutorial 07: MCP Integrations for Legal Work for connecting Claude to external legal data sources.
Previous: Tutorial 05: Building Custom Negotiation Playbooks