Legal Research MCP Needs Open-Web Context

An r/legaltech post explored a Claude MCP integration with Court Listener. Court Listener is excellent for federal case law open data. The piece missing from most legal-research MCPs is the open-web context layer: analyst commentary, regulatory news, professional opinion, Reddit r/legaltech threads where amendments are debated days before mainstream coverage.

The two layers of legal research

• Authoritative data. PACER, Westlaw, LexisNexis, Court Listener for federal cases. EUR-Lex for EU regulation. The source-of-truth layer.
• Open-web context. Analyst takes from law-firm blogs, regulatory news from trade press, professional opinion on r/legaltech and r/europrivacy. The interpretation layer.

Why both matter

A research agent that returns case citations without interpretation produces flat work. A research agent that synthesizes commentary without citing authoritative source produces unreliable work. The right pattern attaches both kinds of MCP server and routes per-query.

The setup

# Authoritative case data
claude mcp add court-listener python /path/to/court-listener-mcp.py

# Open-web context
claude mcp add scavio https://mcp.scavio.dev/mcp \
  --header "x-api-key: $SCAVIO_API_KEY"

The skill prompt

# legal-research.md

For case law lookups (citations, dockets, opinions), call Court
Listener. Cite the case ID and date.

For analyst commentary, regulatory news, draft amendments under
discussion, and community professional opinion, call Scavio.
Use search for mainstream coverage and reddit_search for
r/legaltech, r/europrivacy, r/AskLawyers threads.

Always cite a URL. Mark community sources (Reddit) as such so
the reader can weight them appropriately.

Why Reddit matters for legal research

r/legaltech and r/europrivacy regularly surface draft amendments and proposed regulations days or weeks before mainstream coverage picks them up. Practitioners debate impact before official press releases. A compliance team that catches a draft EU AI Act amendment from r/europrivacy ten days before EUR-Lex publishes the official notice has ten days more to assess impact and draft response.

What does not work

Replacing authoritative data with open-web context. Reddit threads are practitioner debate, not source-of-truth. Court opinions are source-of-truth, not opinion. The agent must respect the layer separation; conflating them produces confidently wrong outputs that get the legal team in trouble.

The cost picture

Court Listener API: free with rate limits. PACER: $0.10/page. Westlaw / LexisNexis: enterprise pricing (typically $5K+/mo per seat). Scavio: $30/mo for 7K credits, free 500/mo. For most paralegal-shaped workflows, the open-web context layer is dramatically cheaper than the authoritative-data layer; the right architecture front-loads Scavio for context and reserves PACER and Westlaw for the actual filings.

The honest constraint

Production legal-research agents need human review before any output goes to a client or filing. The agent surfaces signal; the lawyer or paralegal verifies. Neither MCP layer changes this fact. Treat agent outputs as well-organized notes, not as deliverables.

What this does for the OP

The Court Listener MCP integration the OP is exploring is right but incomplete. Adding Scavio MCP for the open-web context layer takes 30 minutes and turns the agent from a case-lookup tool into a full research assistant. The skill-routing prompt is the deliverable that ties the two layers together.