Best legal-ops tools

Six of the legal systems ooligo tracks expose a working MCP server today — iManage, NetDocuments, Everlaw, Relativity, Docusign, and Thomson Reuters’ CoCounsel Legal — plus CourtListener, which is free and not a commercial product at all. This page ranks them by where MCP pays off right now, and separates what shipped from what was only announced, because the distance between those two is where legal-ops buying goes wrong this year.

Start with the distinction the marketing collapses. “MCP support” in legal means three different things, and they are not interchangeable:

1. A vendor-operated remote server with a published endpoint you point any MCP client at. iManage, NetDocuments, Everlaw, Docusign, and CourtListener sit here. Your assistant choice stays yours.
2. A connector the vendor provisions inside your instance. Relativity sits here. It works, but the vendor stands it up rather than you.
3. A partnership that puts one vendor’s content inside one assistant. Thomson Reuters and Claude sit here. The value is real; the portability is not established.

Anthropic’s Claude for Legal launch on 2026-05-12 shipped more than 20 legal connectors and 12 practice-area plugins on one day, which is why the category reads as bigger than it is. A listing in that directory tells you a system is reachable from Claude. It does not tell you the vendor runs a server you can also reach from Cursor, Codex, or an agent you wrote yourself.

1. iManage — the most portable of the DMS servers

Announced available 2026-05-14. The endpoint is https://cloudimanage.com/mcp/work, OAuth over streamable HTTP, and iManage documents it against Claude Code, Codex, Cursor, and VS Code — not one assistant. Access is authenticated, permission-bound, and logged, and it runs through existing ethical walls instead of around them, which is what gets a firm’s records committee to sign off.

What you get is grounded retrieval over the work product the firm already trusts: matter context and documents read in place, with no bulk export. iManage’s own announcement names Harvey, Legora, ChatGPT, Claude, and Microsoft Copilot as clients. That vendor-neutrality is the real differentiator against everything else on this list.

Watch out: iManage does not publish which tools the server exposes or whether any of them write. Assume read-only until your rep confirms otherwise in writing, and do not scope a workflow that depends on filing documents back.

Where to start: connect one practice group and ask for a precedent search against a live matter. If the answer cites documents the requesting lawyer can already open and nothing else, the ethical-wall story holds.

Full iManage review →

2. CourtListener — primary law with no license conversation

Free Law Project put CourtListener behind a hosted MCP server at https://mcp.courtlistener.com/ on 2026-05-12: case law, PACER dockets, citation analysis, judge data, oral argument transcripts, search, and alerts. Every CourtListener account carries API access automatically, so the cost of trying it is zero and there is no procurement path to walk.

It ranks second because the return per dollar is not close. Every other server here sits behind a subscription you already pay five or six figures for. This one needs an email address and ten minutes.

Watch out: the constraint is throughput, not features. Elevated access runs through a Free Law Project membership or a commercial agreement, so price that before you build a research workflow that assumes volume.

Where to start: add the endpoint to Claude Code or Cursor and run a citation pass over a brief you already filed. You find out quickly whether public data covers your drafting workflow or whether you still need a paid citator.

3. Everlaw — the best-documented server in legal

Everlaw announced its integration on 2026-05-12 and, alone among the vendors here, publishes a real developer reference. The endpoint is https://api.everlaw.com/v1/mcp, OAuth 2.0 with RFC 9728 protected-resource metadata, and it exposes exactly four tools: GetProjectBinders, PostProjectSearch, GetProjectSearchResult, and DescribeProjectSearchTerm. All read-only. Searches combine 20+ terms — Bates ranges, metadata, content text, coding, redactions, productions — with logical operators and grouping, and results page back document IDs, Bates numbers, and review URLs.

Every action runs with the signed-in user’s permissions: the server cannot see or do anything that user could not do in the Everlaw web UI. Rate limits are documented per IP, per access token, per user, and per concurrent tool call, with a stated 60-second retry on the tool-call limit.

Watch out: the server reports itself as version 0.1.0, and search results go stale if documents are added, removed, or edited after you first page a search. Run a fresh search rather than paging an old ID whenever the output feeds something you file.

Where to start: point it at a closed matter and ask for a privilege-log sanity check across a Bates range. Read-only plus a closed matter is the cheapest way to calibrate what the search language can actually express.

Full Everlaw review →

4. NetDocuments — same capability, harder entitlement

NetDocuments hosts a remote MCP endpoint at https://web-api.us.netdocuments.app/connect/mcp, and agents search and retrieve documents on an authenticated user’s behalf. The capability matches iManage’s. The entitlement does not.

ndConnect names two products. Standard ships to every NetDocuments customer and is manual — a person picks documents through a picker into an approved partner app. Enterprise is the MCP tier, and it requires ndMAX Enterprise. NetDocuments dated the expanded connectivity to ndMAX Enterprise customers from 2026-04-01. Independent setup documentation as recent as 2026-07-18 still described organizations needing approval into a limited private preview, and every connecting user needing an active AI 300 seat — the billing unit is people who use AI, not total headcount. NetDocuments’ own integrations page states the Standard-versus-Enterprise split and the ndMAX Enterprise requirement, and states no GA-versus-preview status either way.

Watch out: this is the one entry where “we support MCP” and “you can switch it on this quarter” are different sentences. Get the preview status and the per-connecting-user seat count in writing before you plan a rollout around it.

Where to start: ask your rep two questions — is our organization approved, and what does connecting N lawyers cost in AI 300 seats. Every other decision follows from those two answers.

Full NetDocuments review →

5. Relativity — it writes, but to the workspace, not the evidence

Relativity’s MCP is available now and provisioned by Relativity support into your instance rather than self-served from a public endpoint. What it does is administrative: standing up workspaces, organizing case data, managing matters, adjusting group assignments, reviewing access, and reporting usage. It writes.

The framing matters more than the feature list. Relativity is explicit that MCP and aiR split the work — MCP gets the workspace ready and the team in place, aiR analyzes the evidence inside. A buyer who reads “Relativity supports MCP” as “Claude can review my documents” has the wrong product in mind and will price the wrong thing.

Watch out: admin scope is exactly where a mis-scoped agent does damage, because group assignments are an access-control surface in a matter with a protective order over it. Put write actions behind human approval before pointing an agent at a live workspace.

Where to start: give it a test workspace and have it stand up a matter end to end — workspace, groups, folder structure. That is the task it was built for, and it is the one that saves a project manager a morning.

Full Relativity review →

6. Docusign — the write-capable one, still in beta

Docusign shipped its MCP server at https://mcp-d.docusign.com/mcp alongside the Agreement Manager API and the IAM Toolkit at Momentum 2026. It reaches the Intelligent Agreement Management platform: create, send, and manage agreements, check signing status, query agreement data, and trigger Maestro workflows. Open beta for both developer and production accounts, with no intake form and no approval step.

It is the only entry here that both writes and is self-serve. It is also the only one the vendor labels beta and ships “as is” with no warranty.

Watch out: an agent that sends envelopes is an agent that can send the wrong envelope to the wrong counterparty, and beta is the wrong status under an irreversible action. Keep it read-and-draft until the label comes off, and put a person on the send step.

Where to start: pair it with the Agreement Manager API’s extracted provisions — expiration_date, renewal_type, renewal_notice_date — and build a renewal-exposure report. Read-side value, no transmission risk.

Full Docusign IAM review →

7. CoCounsel Legal — the largest corpus, the least portable connection

Thomson Reuters and Anthropic announced their MCP integration on 2026-05-12, putting 1.9 billion Westlaw and Practical Law documents in reach of Claude for a stated one million-plus legal professionals across 107 countries. The rebuilt CoCounsel Legal runs on Anthropic’s Claude Agent SDK, opened early access in June 2026, and Thomson Reuters put United States general availability in August 2026, with Canada, the UK, and Australia to follow.

Nothing published states that Thomson Reuters operates a server other MCP clients can authenticate against. Every description of the integration runs one direction: Claude connects to CoCounsel Legal. Treat it as a Claude integration rather than a portable server until Thomson Reuters says otherwise.

Watch out: the ranking is about portability, not quality — the corpus here is the strongest on the page. If your firm has already standardized on Claude, this is the highest-value entry on the list and the ranking should not talk you out of it.

Where to start: if you are a US CoCounsel customer, the toggle into the rebuilt experience is in the product. Run one research task both ways and compare the citations, not the prose.

Full CoCounsel review →

What MCP support does not get you

Five assumptions buyers make that the protocol does not support. Each one has a guard.

• It does not get you the AI. These servers supply grounded retrieval; the reasoning belongs to whichever client you connect. Guard: budget the assistant license separately, and never let a DMS vendor’s MCP announcement stand in for an AI evaluation.
• It does not widen permissions — which cuts both ways. Everlaw’s server cannot exceed the signed-in user’s access and iManage’s runs through ethical walls, which is the governance win. It also means an over-broad account produces an over-broad agent. Guard: connect through an identity whose access you have actually audited, not a senior partner’s.
• It does not mean write access. Most legal MCP surfaces are read-heavy. Relativity and Docusign write; Docusign is beta. Guard: confirm scope per server before designing anything that files, sends, or reassigns.
• It does not mean your content stays put. iManage’s own release tells customers to work with their vendors to understand what data leaves iManage through the connection and how it is handled. Permission-bound retrieval is not data residency. Guard: settle destination, retention, and training terms in the DPA before you connect a live matter.
• It does not remove the license cost. NetDocuments is the clearest case: MCP sits behind ndMAX Enterprise and a per-connecting-user AI 300 seat. Guard: price the AI tier per person who will connect, not per firm.

Shipped versus announced, as of 2026-08-17

The minimum viable legal MCP stack

If you want to start with three:

1. Your DMS — iManage or NetDocuments, whichever you already own. This is the one that changes daily work, because it is where the firm’s real answers live.
2. CourtListener — free, and it covers the primary-law floor while you decide whether the paid citator earns its line item.
3. Everlaw or Relativity, if discovery runs in-house. Everlaw for read-side search across project data, Relativity for workspace and matter setup.

Add Docusign the day the beta label comes off. Add CoCounsel Legal on the day you standardize on Claude — not before, because until then you are buying a connection you cannot move.

What’s not on this list (and why)

• Harvey, Legora, and Definely — they appear in Claude for Legal’s connector directory, and Harvey is itself a named client of iManage’s server. They are applications reachable over MCP, not systems of record. Connect them for what they produce, not for grounding.
• Ironclad, Box, Trellis, Midpage, Consilio, and Solve Intelligence — real connectors with narrower scope. Worth adding once the systems above are live; not worth sequencing first.
• Clio, MyCase, and Filevine — the MCP servers that exist for Clio are community-built and third-party, not vendor-operated. That is a different risk profile: you are handing practice-management credentials to someone who is not your vendor and owes you no contract. The enterprise end of the market got vendor servers first, and smaller firms are waiting.
• Microsoft Purview eDiscovery — no vendor MCP server. Its discovery workflows stay inside Microsoft’s own tooling, which is fine if you are M365-resident and a dead end if you wanted a portable connection.