agentic-ops/legal-mcp

Precedent, statute and contract tools for legal workflows

Before you install: no copy-paste command · no license recorded · site blocks automated checks

First step: pip install -r requirements.txt

View on GitHub ↗Link checked 2026-11-12 · automated check blocked (HTTP 429), status unconfirmed

Install & config

Client config (built from the install command this repo gives)

{
  "mcpServers": {
    "agentic-ops-legal-mcp": {
      "command": "npx",
      "args": ["@modelcontextprotocol/inspector"]
    }
  }
}

Parsed from the README we fetched on 2026-11-07; we have not executed it.

command/args come from the install command the repository states. When it is ambiguous, the project README wins.

VS Code (.vscode/mcp.json - the key is servers)

{
  "servers": {
    "agentic-ops-legal-mcp": {
      "command": "npx",
      "args": ["@modelcontextprotocol/inspector"]
    }
  }
}

Same server, but VS Code keeps it under <code>servers</code>.

Claude Code (command line)

claude mcp add --transport stdio agentic-ops-legal-mcp -- npx @modelcontextprotocol/inspector

Claude Code does not read a config file; add the server with this command.

Key names differ by client: Clients & CLI

Source: collected from the abordage/awesome-mcp list · type: MCP server
Harvest history: first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score: score 1,003 · 10 sources · mcp
Install: npx @modelcontextprotocol/inspector

FAQ (answers come from our records)

How do I install it?

The repository provides this install command: npx @modelcontextprotocol/inspector. It comes from the repository itself; we cannot guarantee it runs as-is in your client.

Who is it for?

We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.

Who maintains it?

first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# Legal MCP Server — Research, Paralegal & Workflow Automation

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

A Model Context Protocol (MCP) server for
structured legal workflows. This legal MCP server provides tools, resources,
and prompts for precedent retrieval, statute analysis, citation validation,
contract clause comparison, and guided brief scaffolding. Production mode is
the default: bundled sample legal content is disabled, while real-document
tools and optional opt-in live legal databases remain available.
> This server provides legal‑workflow augmentation, not legal advice. It
> does not replace attorney review and judgment.
Status: V1 — implemented and tested.
Transport: stdio, SSE, and streamable‑HTTP (via FastMCP).
Runtime: Python 3.10+ and the official mcp SDK.
## Contents
Data flow & privacy boundaries
PACER and paid‑database fees (read first)
Quick start
Capabilities
Feature flags (tool categories)
Live integrations (PACER & CourtListener/RECAP)
Docker (optional)
Use as an Agent Skill (Claude, Cursor, Codex, and more)
Built on legal-mcp (showcase)
Forking & building your own
Architecture
Testing, linting & types
Legal & compliance notes
AI agent privacy considerations
Further reading
Integration & development support
License
## Data flow & privacy boundaries
Understanding where data goes is essential before connecting this server to
an AI assistant or enabling live integrations. The diagram below shows the
three separate trust boundaries involved in a typical workflow.
mermaid
flowchart LR
user[User]
aiClient[AI Assistant]
inference[Inference Provider]
mcpServer[Legal MCP Server]
localData[Real local files]
demoData[Opt-in demo content]
courtlistener[CourtListener / RECAP]
pacer[PACER]
user -->|"prompts and documents"| aiClient
aiClient -->|"full conversation context"| inference
aiClient |"MCP tool calls and JSON responses"| mcpServer
mcpServer -->|"local processing"| localData
mcpServer -.->|"explicit demo mode"| demoData
mcpServer -.->|"opt-in, free"| courtlistener
mcpServer -.->|"opt-in, billable"| pacer
| Boundary | What crosses it | Default behavior | Privacy note |
| You → AI assistant | Prompts, uploaded files, tool results pasted into chat | Always active when using an AI client | Your inference provider's ToS governs retention, training, and privilege — not this server |
| AI assistant → MCP server | Tool arguments (file paths, queries, contract IDs) and JSON responses | Local transport (stdio/SSE/HTTP on your machine) | Tool calls are audit-logged locally (utils.audit); responses stay on your network unless you expose the server |
| MCP server → external databases | Search queries to CourtListener or PACER | Disabled by default | Enable only when needed; PACER may incur fees (see below) |
Key takeaway: this MCP server performs local document workflows offline by
default. It does not expose the bundled sample cases, statutes, or contracts
unless LEGAL_MCP_DEMO_MODE=true is explicitly set.
The highest privacy risk in most setups is the inference provider (OpenAI,
Anthropic, Google, OpenRouter, etc.) receiving your full prompt context —
including excerpts returned by these tools. See
AI agent privacy considerations for
provider-specific guidance.
## ⚠️ PACER and paid‑database fees (read first)
If you connect this MCP (or an AI assistant using it) to PACER or other paid

Listed badge (optional)

Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.

[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/agentic-ops-legal-mcp/)

Source: awesome · https://github.com/agentic-ops/legal-mcp
Browse by field: MCP servers
Listed by: 10 independent sources
added: today

More like this

flux159/mcp-server-kubernetesMCP server ndthanhdev/mcp-browser-kitMCP server microsoft/playwright-mcpMCP server juspay/neurolinkMCP server

All 6,229 →

Filed under

MCP servers6,229 entries MCP server6,545 Curated list pick6,618

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index