Everlaw MCP Server

The Everlaw MCP server is an officially hosted remote MCP server from Everlaw, the cloud-based ediscovery and litigation platform. It lets Model Context Protocol clients such as Claude Desktop, Claude Code, Cursor, and other MCP hosts read project data and run searches on behalf of a signed-in Everlaw user. Legal teams can search, retrieve, and analyze case materials directly inside their AI client while Everlaw remains the governed system of record.

The server is a standards-compliant OAuth 2.0 authorization server with RFC 9728 protected-resource metadata, so MCP clients that implement the standard discovery flow can connect with no manual setup beyond the resource URL. The API host (api.everlaw.com) and the authorization server (app.everlaw.com) are separate, and a single MCP scope grants access to all server tools. All actions execute with the signed-in user's permissions, so the server cannot see or do anything the user could not do in the Everlaw web UI.

Currently the server exposes four read-oriented tools that cover binder enumeration, saved-search-quality querying with 20+ search terms and logical grouping, paginated result retrieval (document IDs, Bates numbers, review URLs, metadata, text, or AI-extracted values), and search-term schema introspection. It is available in Claude's Connector Directory for mutual Everlaw and Anthropic customers.

Tools

Prerequisites

• An active Everlaw account with access to at least one project (read access required for binder and search tools; org-admin access also works where the project database permits)
• An MCP client that supports remote MCP servers with OAuth 2.0 discovery (Claude Desktop, Claude.ai, Claude Code, Cursor, etc.)
• For Claude.ai, your workspace must be a mutual Everlaw and Anthropic customer with the Everlaw connector enabled

Connecting from Claude.ai (Connector Directory)

1. Log into Claude.ai and open the connector settings. Follow Claude's "Use connectors to extend Claude's capabilities" guide to add the Everlaw connector.
2. Click Connect on the Everlaw connector. You will be redirected to the Everlaw login page at app.everlaw.com.
3. Log into Everlaw with your normal credentials (including SSO if configured by your org).
4. On the authorization screen, grant the MCP scope to claude.ai by clicking Allow.

Connecting from a generic MCP client

The server is a standards-compliant OAuth 2.0 server. Clients that implement the standard discovery flow only need the resource URL. OAuth metadata is published at:

https://app.everlaw.com/.well-known/oauth-authorization-server

This document advertises the authorization, token, introspection, revocation, and JWKS endpoints (RFC 8414). The API host is api.everlaw.com and the auth host is app.everlaw.com.

Example Claude Desktop config using mcp-remote as a bridge (replace the resource URL with the one published by Everlaw for your region, e.g. api.everlaw.co.uk for UK):

{
  "mcpServers": {
    "everlaw": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.everlaw.com/mcp"
      ]
    }
  }
}

On first use the client will open a browser window to complete the OAuth flow against app.everlaw.com. Confirm the exact resource URL with Everlaw's MCP Server knowledge base article before deploying.

Scopes and permissions

• Single scope: MCP grants access to all four tools
• Tool calls execute as the signed-in user, respecting Everlaw project, binder, and database permissions
• GetProjectBinders, PostProjectSearch, and GetProjectSearchResult require read access on the target project; DescribeProjectSearchTerm does not

• Natural-language ediscovery search: Ask Claude to run complex searches across an Everlaw project combining 20+ search terms with logical operators, then retrieve Bates numbers and review URLs for the hits.
• Deposition and trial prep: Filter project documents by author, custodian, date range, or content and surface candidates for inclusion in a binder before manually creating it in Everlaw.
• Document lookup by Bates number: Retrieve specific documents with their metadata, text, or AI-extracted values directly inside the chat for review or summarization.
• Project triage and reporting: Enumerate binders, run counting searches, and produce summary metrics or visualizations of project state without leaving the AI client.
• Multi-step investigation workflows: Chain DescribeProjectSearchTerm to learn a term's schema, run PostProjectSearch, then page through GetProjectSearchResult to drive structured analysis.

• "List all binders in my Everlaw project 12345 and tell me which ones the lead associate owns."
• "Search the Acme matter for emails from john@acme.com between Jan and March 2024 that mention 'merger' or 'acquisition' and return the Bates numbers."
• "Describe the schema for the content search term so I can build a proximity query."
• "Find every document tagged as privileged in the Smith v. Jones project and summarize the metadata."
• "Run a search for any document group containing the keyword 'NDA' and pull the first 50 results with their review URLs."

• Officially built and hosted by Everlaw, with first-party support and OAuth 2.0 protected by Everlaw's existing auth (including SSO)
• Listed in Claude's Connector Directory, so onboarding for Claude.ai users is essentially zero-config
• Enforces the signed-in user's permissions end-to-end; the AI cannot see anything the user could not see in the web UI
• Supports rich, saved-search-quality queries (20+ search terms with grouping and logical operators) rather than simple keyword lookup

• Read-only: the four tools cover search and retrieval but cannot create binders, apply codes, or modify project data from the MCP client
• Restricted to mutual Everlaw and Anthropic customers via the Connector Directory; other MCP clients must use the OAuth discovery flow manually
• Small tool surface today (four tools), so workflows beyond search and document retrieval still require the Everlaw web UI or REST API

• Everlaw REST API (api.everlaw.com/docs/): full read/write programmatic access if you need actions beyond search and retrieval
• Relativity aiR / Relativity REST API: comparable ediscovery platform with its own AI and API surface for similar workflows
• Community ediscovery MCP servers: a few open-source MCP wrappers exist for other litigation platforms, but no official MCP server competes directly with Everlaw's first-party offering