Skip to main content
Legalai.guide
Advanced

Tutorial 07: MCP Integrations for Legal Workflows

Connect Claude to case law databases, document management systems, and court records for seamless legal research workflows using the Model Context Protocol.

Learning Objectives

By the end of this tutorial, you will:

  • Understand the Model Context Protocol (MCP) and its legal applications
  • Set up Midpage for case law research integration
  • Connect to document management systems (iManage, Clio, SharePoint)
  • Build custom legal research workflows with MCP
  • Execute statutory research workflows with version tracking
  • Implement automated citation verification processes
  • Set up court records alerts and docket monitoring
  • Apply agentic multi-step research patterns
  • Interpret case law analytics for strategic insights

Advanced Level | Some Technical Comfort Required | Time: 105 minutes


What Is MCP?

Model Context Protocol (MCP) is Anthropic's open standard for connecting AI to external tools and data sources. Think of it as USB for AI—a universal connector.

Traditional ApproachMCP Approach
Copy-paste from Westlaw to ClaudeClaude queries Westlaw directly
Download from iManage, upload to ClaudeClaude accesses iManage directly
Switch between 5 different toolsSingle interface with all tools
Manual data entryAutomated data flow
ServerFunctionStatus
MidpageCase law researchProduction
CourtListenerFree case law databaseOpen source
LegalContextClio document accessProduction
French Legal ResearchFrench law databaseProduction
iManageDocument managementVia API
SharePointDocument storageBuilt-in
Congress APILegislative trackingOpen source
PACERFederal court recordsOpen source
Google ScholarCitation verificationOpen source
RECAPCourt filing alertsOpen source

Part 2: Setting Up Midpage Integration

What Midpage Provides

Midpage is a legal research platform with AI-powered features:

  • Comprehensive US case law database
  • AI-powered citator (good law verification)
  • Semantic search across case law
  • Citation extraction and validation

Integration Benefits

With Midpage + Claude:

  • Research case law without leaving Claude
  • Verify citations are still good law
  • Find relevant precedents for your facts
  • Draft with integrated legal authority

Requirements

  • Midpage subscription
  • Claude Pro, Team, or Enterprise
  • Claude Desktop app

Setup Steps

Step 1: Get Midpage API Credentials

  1. Log into Midpage dashboard
  2. Navigate to Settings → API Access
  3. Generate API key
  4. Copy key securely

Step 2: Configure in Claude Desktop

Open Claude Desktop settings and add MCP server:

{
  "mcpServers": {
    "midpage": {
      "command": "npx",
      "args": ["-y", "@midpage/mcp-server"],
      "env": {
        "MIDPAGE_API_KEY": "your-api-key-here"
      }
    }
  }
}

Step 3: Verify Connection

In Claude, test the connection:

Can you search Midpage for recent California Supreme Court
cases on non-compete agreements?

You should see Claude query Midpage and return case citations.

Usage Examples

Example 1: Case Law Research

I'm drafting a motion to compel arbitration in Texas.
Search Midpage for the leading Texas cases on
arbitration enforceability and summarize the current standards.

Example 2: Citation Verification

I want to cite Johnson v. Smith Corp., 234 F.3d 567 (5th Cir. 2020)
in my brief. Use Midpage to verify this citation is still good law.

Example 3: Finding Supporting Authority

My client was terminated after reporting safety violations.
Search Midpage for Texas whistleblower retaliation cases where
the plaintiff prevailed. Focus on cases from the last 5 years.

Privacy & Security

  • Midpage is SOC 2 compliant
  • They cannot see your full Claude conversations
  • They only see which searches/cases you access
  • Data is not used for training

Part 3: Setting Up CourtListener (Free Alternative)

What CourtListener Provides

CourtListener is a free, open-source legal research database:

  • Federal case law
  • State court opinions
  • Oral arguments
  • PACER integration
  • No subscription required

Setup Steps

Step 1: Install CourtListener MCP

npm install -g @open-legal-tools/courtlistener-mcp

Step 2: Configure in Claude

{
  "mcpServers": {
    "courtlistener": {
      "command": "courtlistener-mcp",
      "args": ["serve"],
      "env": {
        "COURTLISTENER_API_KEY": "your-api-key"
      }
    }
  }
}

The API key is optional but recommended for higher rate limits.

Step 3: Test Connection

Search CourtListener for Ninth Circuit cases discussing
software license enforceability.

CourtListener vs. Midpage

FeatureCourtListenerMidpage
PriceFreeSubscription
CoverageGood federal, variable stateComprehensive
CitatorBasicAI-powered
Update speedSlowerFast
Best forCost-conscious, federal focusFull legal research

Part 4: Document Management Integration

Option A: LegalContext for Clio

LegalContext enables Claude to access documents stored in Clio securely.

Setup:

{
  "mcpServers": {
    "legalcontext": {
      "command": "npx",
      "args": ["-y", "legalcontext-mcp"],
      "env": {
        "CLIO_API_KEY": "your-clio-api-key"
      }
    }
  }
}

Usage:

Retrieve the Smith v. Jones complaint from our Clio matter files
and summarize the key allegations.

Security: Document processing occurs within your firm's security perimeter.

Option B: SharePoint Integration

SharePoint integration is built into Claude Cowork.

Setup:

  1. In Cowork, click "Connect" → SharePoint
  2. Authenticate with Microsoft credentials
  3. Select accessible sites/folders

Usage:

Search our SharePoint legal templates folder for NDAs
and list all templates by date modified.

Option C: iManage via API

iManage integration requires custom setup:

Step 1: Create iManage API Application

  1. Log into iManage Control Center
  2. Create OAuth2 application
  3. Configure redirect URI
  4. Note Client ID and Secret

Step 2: Build Custom MCP Server

// imanage-mcp.js
const { MCPServer } = require('@modelcontextprotocol/sdk');
const iManageClient = require('imanage-api-client');
 
const server = new MCPServer({
  name: 'imanage',
  tools: [
    {
      name: 'search_documents',
      description: 'Search iManage for documents',
      parameters: {
        query: { type: 'string', description: 'Search query' },
        workspace: { type: 'string', description: 'Workspace ID' }
      },
      handler: async ({ query, workspace }) => {
        const client = new iManageClient(process.env.IMANAGE_CREDENTIALS);
        return await client.search({ query, workspace });
      }
    },
    {
      name: 'get_document',
      description: 'Retrieve document content',
      parameters: {
        documentId: { type: 'string', description: 'Document ID' }
      },
      handler: async ({ documentId }) => {
        const client = new iManageClient(process.env.IMANAGE_CREDENTIALS);
        return await client.getDocument(documentId);
      }
    }
  ]
});
 
server.start();

Step 3: Configure in Claude

{
  "mcpServers": {
    "imanage": {
      "command": "node",
      "args": ["path/to/imanage-mcp.js"],
      "env": {
        "IMANAGE_CREDENTIALS": "path/to/credentials.json"
      }
    }
  }
}

Combine multiple MCP sources for thorough research:

I need to research the enforceability of liquidated damages
clauses in software agreements under Delaware law.

Workflow:
1. Search Midpage for Delaware cases on liquidated damages
2. Search CourtListener for federal cases applying Delaware law
3. Pull our firm's memo on liquidated damages from SharePoint
4. Synthesize into a research summary

Claude Response Pattern:

Let me research this across multiple sources...

## Midpage Results (Delaware State Cases)
[Claude queries Midpage, returns cases]

## CourtListener Results (Federal/Delaware Law)
[Claude queries CourtListener, returns additional cases]

## Firm Precedent (SharePoint)
[Claude retrieves firm memo]

## Synthesis
Based on my research across these sources:

The leading Delaware case is [X], which established...
Federal courts applying Delaware law have held...
Our firm's prior analysis in the [Client] matter noted...

**Key Takeaways**:
1. Delaware generally enforces liquidated damages if...
2. The "reasonableness" test requires...
3. Our recommended approach is...

**Citations** (verified via Midpage citator):
- [Citation 1] - Still good law
- [Citation 2] - Still good law

Workflow 2: Contract + Research Integration

/review-contract
[Upload software agreement]

[Claude identifies concerning liability provision under CA law]

"I've flagged the liability limitation as potentially problematic.
Let me research California's position on liability caps in
software agreements..."

[Claude queries Midpage for CA cases]

"Based on my research, California courts have held that [X].
The clause as drafted may be enforceable because [Y], but
you should consider [Z] modification."

Workflow 3: Due Diligence Research

We're acquiring a company in the healthcare space.
Research the regulatory landscape:

1. Search our SharePoint for prior healthcare M&A memos
2. Search Midpage for recent HIPAA enforcement actions
3. Search for FTC healthcare antitrust cases
4. Generate a due diligence issue checklist

Part 6: Advanced MCP Configuration

Running Multiple MCP Servers

{
  "mcpServers": {
    "midpage": {
      "command": "npx",
      "args": ["-y", "@midpage/mcp-server"],
      "env": { "MIDPAGE_API_KEY": "key1" }
    },
    "courtlistener": {
      "command": "courtlistener-mcp",
      "args": ["serve"]
    },
    "legalcontext": {
      "command": "npx",
      "args": ["-y", "legalcontext-mcp"],
      "env": { "CLIO_API_KEY": "key2" }
    },
    "sharepoint": {
      "command": "npx",
      "args": ["-y", "@microsoft/sharepoint-mcp"]
    }
  }
}

Environment-Specific Configuration

Create different configs for different use cases:

# Legal research config
export CLAUDE_MCP_CONFIG=~/.claude/mcp-research.json
 
# Contract review config
export CLAUDE_MCP_CONFIG=~/.claude/mcp-contracts.json
 
# Full access config
export CLAUDE_MCP_CONFIG=~/.claude/mcp-full.json

Debugging MCP Connections

Check MCP status:

What MCP servers do you have access to right now?
List each server and its available tools.

Test specific tool:

Test the Midpage search tool by searching for "contract breach"
and report any errors.

Part 7: Security Considerations

Data Flow

Your Query

Claude (Anthropic Servers)

MCP Server (Your Control)

External Service (Midpage/iManage/etc.)

Security Best Practices

Credential Management:

  • Never commit API keys to version control
  • Use environment variables
  • Rotate keys regularly
  • Use separate keys for different purposes

Access Control:

  • Limit MCP server access to necessary data
  • Use read-only access where possible
  • Audit MCP server logs
  • Disable unused integrations

Client Data:

  • Understand each service's data handling
  • Check for SOC 2, ISO 27001 certification
  • Review service DPAs
  • Consider which matters can use which integrations

Compliance Checklist

  • All MCP services reviewed for security
  • API keys stored securely
  • Access logs enabled
  • Data processing agreements in place
  • Client consent obtained where required
  • Firm IT approved configuration

Part 8: Statutory Research Workflow

Legislative Tracking Integration

Connect to Congress API for real-time legislative monitoring:

Setup:

{
  "mcpServers": {
    "congress": {
      "command": "npx",
      "args": ["-y", "@open-legal-tools/congress-mcp"],
      "env": {
        "CONGRESS_API_KEY": "optional-api-key"
      }
    }
  }
}

Statute Version Comparison

Workflow for comparing statute versions across legislative sessions:

Research task:
Track amendments to the California CCPA across its
legislative history and identify key changes by session.

Claude multi-step workflow:
1. Query Congress API for CCPA bill history
2. Retrieve full text for versions from 2018, 2020, 2023
3. Compare key sections (scope, penalties, exemptions)
4. Generate side-by-side amendment analysis
5. Flag enforcement implications of changes

MCP Configuration for Statute Tracking:

{
  "mcpServers": {
    "congress": {
      "command": "npx",
      "args": ["-y", "@open-legal-tools/congress-mcp"],
      "tools": [
        "search_bills",
        "get_bill_versions",
        "track_amendments",
        "retrieve_sponsor_info"
      ]
    },
    "regulationtracker": {
      "command": "npx",
      "args": ["-y", "regulation-tracker-mcp"],
      "env": {
        "FEDERAL_REGISTER_API": "api-key"
      }
    }
  }
}

Pattern for comprehensive regulatory research:

Query: "Search all HIPAA regulations (45 CFR 160-164)
related to breach notification requirements and identify
which sections were modified in the last 3 years."

Claude workflow:
1. Query regulatory database for HIPAA sections
2. Cross-reference Federal Register for amendments
3. Pull relevant case law on HIPAA enforcement
4. Compile regulatory timeline
5. Provide implementation checklist for compliance

Bill Tracking Workflows

Set up automated tracking for legislation affecting your practice:

// bill-tracking-mcp.js - Custom MCP for monitoring bills
const server = new MCPServer({
  name: 'bill-tracker',
  tools: [
    {
      name: 'monitor_bills',
      description: 'Set up alerts for bills matching criteria',
      parameters: {
        keywords: { type: 'array', description: 'Bill topic keywords' },
        jurisdictions: { type: 'array', description: 'States/federal' },
        stages: { type: 'array', description: 'Introduced, hearing, floor, etc.' }
      },
      handler: async ({ keywords, jurisdictions, stages }) => {
        // Query Congress API
        // Filter by criteria
        // Return bills with status updates
        return await monitorLegislation(keywords, jurisdictions, stages);
      }
    },
    {
      name: 'compare_versions',
      description: 'Compare bill versions across sessions',
      parameters: {
        billId: { type: 'string' },
        versions: { type: 'array', description: 'Version numbers to compare' }
      },
      handler: async ({ billId, versions }) => {
        return await compareLegislativeVersions(billId, versions);
      }
    }
  ]
});

Part 9: Citation Verification Process

Automated Cite-Checking

Implement citation verification directly in legal writing:

Upload legal brief to Claude with instruction:
"Verify every case citation in this brief is still good law
and identify any corrections needed."

Claude workflow:
1. Extract all citations (Midpage tool)
2. Check each citation status (Midpage citator)
3. Identify overruled/reversed cases
4. Generate citation correction report
5. Flag negative law that contradicts arguments

Good Law Verification System

Configuration for Automated Citation Checking:

{
  "mcpServers": {
    "midpage": {
      "command": "npx",
      "args": ["-y", "@midpage/mcp-server"],
      "tools": [
        "search_cases",
        "verify_citation_status",
        "find_citing_cases",
        "check_negative_law"
      ],
      "env": {
        "MIDPAGE_API_KEY": "your-api-key"
      }
    },
    "google-scholar": {
      "command": "npx",
      "args": ["-y", "google-scholar-mcp"],
      "tools": ["search_scholar", "verify_citations"]
    }
  }
}

Shepardizing/KeyCiting Equivalents

Process for verifying citation authority strength:

Citation verification prompt:
"For the following cases, provide Shepard's analysis:
- Smith v. Jones, 234 F.3d 567 (5th Cir. 2020)
- Brown v. Green Corp., 890 P.2d 123 (Cal. 2019)

For each case:
1. Current status (good law/overruled/limited)
2. Citing cases (positive/negative treatment)
3. Strength of authority for this proposition
4. Alternative authorities if weakened"

Citation Format Validation

Workflow for standardizing citations:

// citation-validator-mcp.js
const server = new MCPServer({
  name: 'citation-validator',
  tools: [
    {
      name: 'validate_citation_format',
      description: 'Validate and standardize citation format',
      parameters: {
        citation: { type: 'string', description: 'Citation to validate' },
        jurisdiction: { type: 'string', description: 'State/federal' },
        citationStyle: { type: 'string', enum: ['bluebook', 'alwd', 'local'] }
      },
      handler: async ({ citation, jurisdiction, citationStyle }) => {
        const normalized = normalizeCitation(citation, jurisdiction);
        const formatted = applyCitationStyle(normalized, citationStyle);
        return {
          original: citation,
          normalized,
          formatted,
          isValid: true,
          corrections: []
        };
      }
    },
    {
      name: 'batch_validate_brief',
      description: 'Validate all citations in document',
      parameters: {
        documentText: { type: 'string' },
        citationStyle: { type: 'string' }
      },
      handler: async ({ documentText, citationStyle }) => {
        const citations = extractCitations(documentText);
        const validated = await Promise.all(
          citations.map(c => validateCitationFormat(c, citationStyle))
        );
        return {
          totalCitations: citations.length,
          validCitations: validated.filter(v => v.isValid).length,
          issues: validated.filter(v => !v.isValid),
          correctedDocument: reconstructDocumentWithCorrections(documentText, validated)
        };
      }
    }
  ]
});

Part 10: Court Records Alert Setup

Real-Time Case Filing Alerts

Configure PACER integration for docket monitoring:

Setup PACER MCP Server:

{
  "mcpServers": {
    "pacer": {
      "command": "npx",
      "args": ["-y", "@open-legal-tools/pacer-mcp"],
      "env": {
        "PACER_USERNAME": "your-pacer-login",
        "PACER_PASSWORD": "your-pacer-password",
        "PACER_CLIENT_CODE": "your-client-code"
      }
    },
    "recap": {
      "command": "npx",
      "args": ["-y", "@free-law-project/recap-mcp"],
      "tools": [
        "search_pacer_documents",
        "get_docket",
        "set_filing_alerts",
        "get_document"
      ]
    }
  }
}

850M+ Record Search Patterns

Query patterns for comprehensive court records search:

Workflow: Competitive intelligence monitoring

Setup alert for:
- All cases involving Company X in federal courts
- Parties: Company X (plaintiff or defendant)
- Date range: Last 2 years
- Alert frequency: Real-time

Claude multi-source search:
1. Query PACER for Company X docket entries
2. Search RECAP for public documents
3. Cross-reference state court records
4. Extract defendants/plaintiffs for analysis
5. Generate competitive threat assessment

Large-Scale Search Configuration:

# Search patterns for 850M+ document database
# Example: Patent litigation involving software
 
curl -X POST https://api.recap.org/search \
  -H "Content-Type: application/json" \
  -d '{
    "query": "software patent infringement",
    "courts": ["all_federal"],
    "date_filed_after": "2023-01-01",
    "document_types": ["complaint", "judgment"],
    "limit": 1000
  }'

Docket Monitoring

Automated docket tracking workflow:

Monitor docket: Smith v. Jones, Case No. 2023-CV-12345

Daily workflow:
1. Check for new filings (PACER alert)
2. Extract filing metadata (date, filer, document type)
3. Download documents if Rule 34 request received
4. Flag critical events (depositions, trial dates)
5. Summarize for team

Configuration:
{
  "monitored_dockets": [
    {
      "case_id": "2023-CV-12345",
      "court": "Northern District of California",
      "check_frequency": "daily",
      "alerts": {
        "critical_events": true,
        "discovery_deadlines": true,
        "expert_disclosures": true,
        "all_filings": false
      }
    }
  ]
}

Party-Based Tracking

Monitor all matters involving specific parties:

// party-tracker-mcp.js
const server = new MCPServer({
  name: 'party-tracker',
  tools: [
    {
      name: 'track_party',
      description: 'Monitor all cases involving a party',
      parameters: {
        partyName: { type: 'string', description: 'Individual or company name' },
        role: { type: 'string', enum: ['plaintiff', 'defendant', 'all'] },
        courts: { type: 'array', description: 'Courts to monitor' }
      },
      handler: async ({ partyName, role, courts }) => {
        const cases = await searchAllCourts(partyName, role, courts);
        const dockets = await Promise.all(cases.map(c => getDocket(c.caseId)));
        return {
          totalCases: cases.length,
          activeCases: cases.filter(c => c.status === 'open'),
          dockets,
          competitiveAnalysis: analyzePartyHistory(cases)
        };
      }
    }
  ]
});

Part 11: Agentic Multi-Step Research Pattern

Execute complex research tasks with agent-like behavior:

Research request:
"My client is negotiating a software licensing agreement
with a major tech company. Research the landscape of:
1. Recent software licensing disputes
2. Key contract provisions courts scrutinize
3. Best practices from firm precedents
4. Relevant patent litigation affecting licensing
5. Synthesize into deal negotiation memo"

Claude agent workflow:
Step 1: Research Phase
  - Query Midpage for software licensing cases (last 5 years)
  - Extract critical issues from leading cases

Step 2: Precedent Phase
  - Search SharePoint for firm's prior licensing agreements
  - Extract successful clause language
  - Identify deal-breaker provisions by client type

Step 3: Patent Phase
  - Search Google Patents for relevant technology patents
  - Identify software licensing implications
  - Flag cross-license requirements

Step 4: Synthesis Phase
  - Organize findings by provision (IP ownership, liability, etc.)
  - Cross-reference case law to deal terms
  - Generate risk assessment matrix

Step 5: Deliverable Phase
  - Create negotiation memo with:
    * Market landscape summary
    * Key case takeaways
    * Recommended provisions
    * Risk mitigation strategies

Multi-Source Synthesis

Configuration for coordinated research across sources:

{
  "mcpServers": {
    "midpage": { },
    "sharepoint": { },
    "google-patents": {
      "command": "npx",
      "args": ["-y", "google-patents-mcp"]
    },
    "courtlistener": { }
  },
  "research_workflows": {
    "licensing_negotiation": {
      "sources": ["midpage", "sharepoint", "google-patents"],
      "steps": [
        "search_cases",
        "extract_precedents",
        "patent_analysis",
        "synthesize_findings"
      ],
      "output_format": "negotiation_memo"
    }
  }
}

Research Plan Generation

Workflow for automatic research planning:

User: "I need to understand California's position on
non-compete agreements in employment contracts.
What should I research?"

Claude research planner:
"I'll develop a research plan covering:

Phase 1: Controlling Authority
  - California Supreme Court cases on non-competes
  - Test: Is non-compete reasonable? (Blue Pencil doctrine)
  - Key cases: Silguero, Edwards, Morbi

Phase 2: Legislature Response
  - California Business & Professions Code § 16600
  - Legislative amendments (2024 updates)
  - Statutory interpretation

Phase 3: Modern Applications
  - Recent Court of Appeal decisions (2023-2025)
  - Non-compete vs. non-solicitation distinction
  - Remote work implications

Phase 4: Practical Synthesis
  - Enforceable provisions despite § 16600
  - Trade secret protection alternatives
  - Employment agreement drafting best practices

Estimated research time: 2-3 hours
Key sources: Midpage, Clio firm memos, Bar Association guidance"

Iterative Refinement

Build research workflows that improve with each iteration:

# research_refinement_pattern.py
research_iteration = {
    "initial_query": "California non-compete enforceability",
 
    "iteration_1": {
        "findings": "Initial results show non-competes generally unenforceable",
        "questions_raised": [
            "What about legitimate business interests exception?",
            "How does this apply to C-suite executives?",
            "Recent trends in remote work?"
        ]
    },
 
    "iteration_2": {
        "refined_searches": [
            "California non-compete exceptions legitimate business interests",
            "Non-compete enforcement executive employment contracts",
            "Non-compete non-solicitation remote work 2024"
        ],
        "new_findings": "Narrow exceptions for limited legitimate interests",
        "additional_questions": [
            "What qualifies as legitimate business interest?",
            "How do courts balance employee freedom with employer protection?"
        ]
    },
 
    "iteration_3": {
        "targeted_research": [
            "California Business Code § 16600 case law interpretation",
            "Blue pencil doctrine in non-compete context",
            "Employer strategic alternatives to non-competes"
        ],
        "synthesis": "Actionable guidance for client"
    }
}

Part 12: Case Law Analytics Interpretation

Judge Behavior Analytics

Integrate judicial analytics for litigation strategy:

Query: "Judge Smith handles patent licensing disputes
in the Northern District of California. What patterns
can I identify in her decisions?"

Analytics workflow:
1. Search RECAP for all Judge Smith cases
2. Extract relevant patent licensing decisions
3. Analyze patterns:
   - Grant rate on summary judgment motions
   - Treatment of injunction requests
   - Damages awards (high/low/reasonable)
   - Attitude toward expert witnesses
4. Compare to district averages
5. Generate litigation strategy recommendations

Configuration for Judicial Analytics:

{
  "mcpServers": {
    "judicial-analytics": {
      "command": "npx",
      "args": ["-y", "judicial-analytics-mcp"],
      "tools": [
        "judge_profile",
        "decision_patterns",
        "motion_grant_rates",
        "remedy_analysis",
        "compare_judges"
      ],
      "env": {
        "RECAP_API": "api-key",
        "COURTLISTENER_API": "api-key"
      }
    }
  }
}

Attorney Performance Data

Track opposing counsel patterns:

Workflow: Opposing Counsel Analysis

For: Attorney Jane Doe (plaintiff's counsel)

Metrics extracted:
- Settlement rate: 45% (vs. district average 52%)
- Trial win rate: 62% (favorable)
- Average verdict: $1.2M (high-value cases)
- Expert witness preferences: Specific firms used repeatedly
- Motion practice: Aggressive discovery requests
- Deposition style: Confrontational

Strategic implications:
- Prepare for aggressive discovery
- Expect push to trial
- May be open to structured settlements
- Anticipated expert witnesses based on historical patterns

Outcome Prediction Patterns

Machine learning-assisted outcome prediction:

Query: "Predict the likely outcome of our employment
discrimination case with Judge Smith in NDCA."

Analysis:
1. Historical data: Judge Smith's discrimination cases
2. Factors: Strength of evidence, damages, settlement history
3. Prediction: 65% chance of plaintiff success in trial
4. Outcome distribution:
   - Summary judgment win (defendant): 20%
   - Trial win (defendant): 15%
   - Trial win (plaintiff): 45%
   - Settlement: 20%
5. Median award if plaintiff prevails: $850,000
6. Confidence interval: +/- $300,000

Settlement Range Analysis

Data-driven settlement valuation:

// settlement-analytics-mcp.js
const server = new MCPServer({
  name: 'settlement-analytics',
  tools: [
    {
      name: 'predict_settlement_range',
      description: 'Analyze historical settlements for range prediction',
      parameters: {
        caseType: { type: 'string', description: 'Employment, IP, contract, etc.' },
        jurisdiction: { type: 'string' },
        judge: { type: 'string' },
        damages: { type: 'number', description: 'Claimed damages' }
      },
      handler: async ({ caseType, jurisdiction, judge, damages }) => {
        const historicalCases = await searchSimilarCases(
          caseType, jurisdiction, judge
        );
        const settlementRates = analyzeSettlements(historicalCases);
        const predictedRange = calculateRange(
          damages,
          settlementRates,
          judge
        );
        return {
          predictedLowRange: predictedRange.low,
          predictedMidRange: predictedRange.mid,
          predictedHighRange: predictedRange.high,
          confidence: predictedRange.confidence,
          comparableCases: historicalCases.slice(0, 5)
        };
      }
    }
  ]
});

Part 13: Comparison to Enterprise Solutions

Claude + MCP vs. Harvey Integration

AspectClaude + MCPHarvey
SetupDIY or simple configVendor-managed
CustomizationFull controlLimited
Research sourcesChoose your ownHarvey's selected sources
Document managementConnect any systemHarvey Vault only
CostPay per serviceAll-in-one pricing
MaintenanceYou manageHarvey manages

When to Choose Each

Choose Claude + MCP when:

  • You want control over integrations
  • Cost is a significant factor
  • You have IT resources for setup
  • You use non-standard tools

Choose Harvey/Legora when:

  • You want turnkey solution
  • Enterprise support is required
  • Budget allows premium pricing
  • You need vendor accountability

Homework Before Tutorial 08

  1. Set up at least two MCP integrations (Midpage, CourtListener, PACER, or Congress API)
  2. Test comprehensive legal research with your MCP connections
  3. Execute a citation verification workflow using Midpage citator
  4. Implement a multi-source research workflow combining 3+ sources
  5. Test judicial analytics by researching a judge's decision patterns
  6. Build a statutory research workflow tracking legislation in your practice area
  7. Document your MCP configuration for team reference and updates
  8. Create a research playbook documenting your standard workflows

Quick Reference: MCP Server Commands

Midpage

Search for [topic] cases in [jurisdiction]
Verify citation [citation] is still good law
Find cases that cite [case name]
Check if [case] has been overruled or limited

CourtListener

Search CourtListener for [query]
Get full text of [case citation]
Find oral arguments in [case]
Search by judge: [judge name] in [court]

Legislative & Regulatory

Search Congress for bills matching [criteria]
Track amendments to [statute] by year
Compare versions of [bill] across sessions
Search Federal Register for [regulation changes]
Monitor bills in [state legislature] related to [topic]

Court Records

Search PACER for cases involving [party name]
Get docket for [case number] in [court]
Set alert for filings in [case number]
Search RECAP for [party] across all federal courts
Find all cases by Judge [judge name]

Citation Verification

Verify citation [citation] is still good law
Check Shepard's for [case]: positive/negative treatment
Find alternative authorities for [proposition]
Validate citation format for [citation] (Bluebook/ALWD)

Document Management

Search [system] for documents matching [criteria]
Retrieve document [name/ID] from [location]
List recent documents in [workspace/folder]

Analytics & Insights

Analyze Judge [judge name] decision patterns for [case type]
Predict settlement range for [case type] before Judge [judge]
Compare outcome patterns for opposing counsel [attorney name]
Calculate motion grant rates for [judge] on [motion type]

Sources


← Previous: Legal Plugin | Next: Cowork Automation →

On this page

Learning ObjectivesPart 1: Understanding MCP for LegalWhat Is MCP?Why MCP Matters for LegalAvailable Legal MCP ServersPart 2: Setting Up Midpage IntegrationWhat Midpage ProvidesIntegration BenefitsRequirementsSetup StepsUsage ExamplesPrivacy & SecurityPart 3: Setting Up CourtListener (Free Alternative)What CourtListener ProvidesSetup StepsCourtListener vs. MidpagePart 4: Document Management IntegrationOption A: LegalContext for ClioOption B: SharePoint IntegrationOption C: iManage via APIPart 5: Building Legal Research WorkflowsWorkflow 1: Comprehensive Legal ResearchWorkflow 2: Contract + Research IntegrationWorkflow 3: Due Diligence ResearchPart 6: Advanced MCP ConfigurationRunning Multiple MCP ServersEnvironment-Specific ConfigurationDebugging MCP ConnectionsPart 7: Security ConsiderationsData FlowSecurity Best PracticesCompliance ChecklistPart 8: Statutory Research WorkflowLegislative Tracking IntegrationStatute Version ComparisonRegulatory Code SearchBill Tracking WorkflowsPart 9: Citation Verification ProcessAutomated Cite-CheckingGood Law Verification SystemShepardizing/KeyCiting EquivalentsCitation Format ValidationPart 10: Court Records Alert SetupReal-Time Case Filing Alerts850M+ Record Search PatternsDocket MonitoringParty-Based TrackingPart 11: Agentic Multi-Step Research PatternDeep Legal Research WorkflowsMulti-Source SynthesisResearch Plan GenerationIterative RefinementPart 12: Case Law Analytics InterpretationJudge Behavior AnalyticsAttorney Performance DataOutcome Prediction PatternsSettlement Range AnalysisPart 13: Comparison to Enterprise SolutionsClaude + MCP vs. Harvey IntegrationWhen to Choose EachHomework Before Tutorial 08Quick Reference: MCP Server CommandsMidpageCourtListenerLegislative & RegulatoryCourt RecordsCitation VerificationDocument ManagementAnalytics & InsightsSources