Everlaw

Search an Everlaw eDiscovery project and page through documents.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Everlaw connector does

The Everlaw MCP server connects an Everlaw eDiscovery project — the litigation document platform where discovery material is reviewed, coded and produced — to Claude, ChatGPT and any MCP-compatible agent. It runs saved-search-quality queries, pages through matching documents and returns Bates numbers, metadata and review links. Everlaw states the connection is read-only.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Everlaw tools (3)

  • GetProjectSearchResult
  • PostProjectSearch
  • GetProjectBinders

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Everlaw states Claude cannot search the specific codes or ratings applied to documents, or who applied redactions or highlights; search the contents of stored translations; view or analyze images and non-text content; take actions reflected within Everlaw such as applying redactions or codes; access information about project users or analytics; connect to Storybuilder; or use Deep Dive to answer a question.
  • Search quality degrades in specific, documented ways. Everlaw warns that Claude does not reliably treat quotation marks as an exact-phrase directive, that proximity searches "typically do not work well without additional instruction", that it will not correct a typo in a contents query, that it defaults to UTC rather than the project time zone, and that it uses binary rather than Everlaw's decimal size definitions. Everlaw publishes a Claude Project instructions block to correct all five. In litigation a silently under-inclusive search is the failure that matters, and these are exactly that shape.
  • Results can be stale. Everlaw documents that GetProjectSearchResult may return stale results if documents were added, removed or edited, or the search itself edited, after the endpoint was first called for that search. Its guidance is to run a new search before paging.
  • Volume ceilings. Everlaw says Claude may struggle with questions spanning many documents, and with visualizations of more than 4,000 documents.
  • The directory listing is incomplete. Three tools are listed against eight documented and eighteen named. We did not verify the larger figures against the server.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request. Parameter detail on this page comes from Everlaw's developer reference, not from the server.
  • The published scope contract does not match the deployed one. Everlaw's reference documents a single MCP scope; the live descriptor advertises 13, three of them writes. We could not determine which the consent screen actually presents.
  • No dynamic client registration. Everlaw's authorization server metadata declares no registration_endpoint, so clients requiring DCR-based OAuth cannot self-register.
  • US environment only, and not GovCloud. Everlaw's admin documentation confirms OAuth2 itself is unavailable in GovCloud.
  • Nothing observes cost. No tool reads billing or usage, though BILLING_READ is among the advertised scopes and PostProjectSearch can compute a BILLABLE_SIZE metric. Everlaw documents no per-call charge for the connector, so we found no spend to observe.
  • Everlaw's marketing and its documentation describe different surfaces. Its integration blog post says users "can directly control Everlaw and execute Everlaw actions within Claude" and describes assembling a virtual exhibit binder. The documentation says the connection is read-only and lists no tool that creates a binder. The documentation is the accurate source; read the blog's "actions" as searches and its "binder" as a Claude-side table.

Frequently asked questions

Is the Everlaw MCP connector read-only?

Everlaw says yes, in three separate documents. Its help centre states the connection is read-only and that you cannot modify, export or delete documents from Claude. Every tool Everlaw documents is a Get, a Post that runs a search, or a Describe. No tool codes a document, edits a production set or changes a review decision.

Why does the Everlaw OAuth descriptor advertise write scopes?

Because it is the platform-wide scope catalogue, not an MCP-specific one. Everlaw's protected-resource document at the MCP path advertised thirteen scopes on 2026-08-23, including DATA_WRITE, LEGAL_HOLD_WRITE and USER_MANAGEMENT_WRITE. The identical list appears at the API root, so it describes the whole Everlaw API rather than the connector's surface.

How many tools does the Everlaw MCP server actually have?

Three is Anthropic's count and it understates the surface. Everlaw's developer reference fully documents eight tools with argument tables, and its search term reference names ten more as sources for query parameters. Everlaw's own end-user guide tells readers to enable four tools that Anthropic's listing omits entirely, so treat three as a floor.

Can Claude read the full text of Everlaw documents?

Only if your Claude administrator opts in. By default the connector returns search results and metadata, so Claude knows a document matched but cannot read the rest of it. Full text requires an Owner or Primary Owner to switch on network egress in Claude and allowlist a specific Amazon S3 domain that hosts the text downloads.

Does the Everlaw connector reach privileged or work-product material?

It can, subject to your own Everlaw permissions. The REVIEW_READ scope covers searching documents and review work product, and search terms cover redactions, coding and production status. Everlaw publishes no warning about privilege waiver anywhere in its MCP documentation, unlike some competing eDiscovery connectors, so no vendor guidance exists on that question.

What do I need before connecting Everlaw to Claude?

An Everlaw Organization Admin must first enable OAuth2 for your organization, because it is off by default. You then need an Everlaw account with access to at least one project in that organization, and a Claude account. Users who connected before 10 June 2026 must have an admin re-enable the new OAuth2 setting.

Which Everlaw regions support the Claude connector?

Only the United States environment. Everlaw states the connection is unavailable to GovCloud users and to customers on its Canada, European Union, United Kingdom and Australia environments. Its admin documentation separately confirms OAuth2 itself is not available in GovCloud, so the restriction is at the authentication layer rather than the connector.

Are there rate limits on the Everlaw MCP server?

Yes, in five layers. Everlaw throttles failed authentication per IP, requests per access token and per authenticated user, each returning HTTP 429. Tool calls are additionally limited per user and by concurrency, surfacing as a tool result with isError true and a message asking you to retry after sixty seconds.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Everlaw to work.

Connect Everlaw once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.