Setup Steps to Use Claude to Search your Everlaw projects

You can now use Claude, Anthropic's AI assistant, to power your Everlaw document searches. 

In this article, we'll cover:

• Guidance for connecting your Everlaw account to your Claude account
• Background details on how Everlaw and Claude connect

For more details about the search capabilities enabled by this connection, as well as some tips and best practices, see our Use Claude to Search and Understand Your Documents article.

Requirements

Pre-requisite: Before you can form the connection, which is done through the Claude interface, an Everlaw Organization Admin must switch on the OAuth2 setting within Everlaw. Once it's switched on, users with access to Everlaw projects within that organization will be able to set up the connection to search them using Claude.

To connect Claude and Everlaw, you must have the following:

• A Claude account
• An Everlaw account with access to at least one project: The searches you do within Claude are limited to the project(s) and documents you have access to.

Data privacy and security

Your data privacy and security is our priority. Your use of Everlaw and our data privacy and security commitments to you are governed by our Terms of Service and Data Processing Addendum.

Your interactions within your Claude environment are governed by your specific customer agreement with Anthropic, which also outlines Anthropic’s security and data privacy practices.

Anthropic is contractually prohibited from using your Everlaw data to train its models. 

Connect Claude to Everlaw

To start using Claude to search your Everlaw documents:

Step 1: An Everlaw Organization Admin must enable OAuth2 within Everlaw. 

Step 2: Once OAuth2 is enabled, any Claude user on projects in that organization can add Everlaw as a connector to their Claude account, then create and authenticate the connection to search those projects from within Claude. This setup is done within Claude.

[Optional] Step 3: An admin in Claude can adjust the allow-listed domains to grant access for Claude to read the full text of individual documents in Everlaw. The instructions on how to do so, and how it differs from the contents searches enabled by default via the MCP connection, are in the section below.

Step 1: Enable OAuth2

This step must be done by an Everlaw Organization Admin. Instructions for how to do so are in the Organization Admin: Everlaw API article.

Step 2: Form the connection

Once OAuth2 is enabled in Everlaw, you can form the connection to Everlaw from within Claude. You can read more about the process in Claude's support documentation. 
To form the connection:

1. Log into your Claude account (web or browser version) and follow the instructions in Claude's Use connectors to extend Claude's capabilities article to add the Everlaw connector.
   • To find the Everlaw connector, follow the instructions in the Browse available connectors section.
   • To set up the connection, follow the instructions in the Connect a service to Claude section.
2. When you select Connect on the Everlaw connector, you are redirected to the Everlaw login page.

3. Log into Everlaw with your Everlaw credentials. 

   Note

   If your Everlaw Organization Admin has not yet enabled OAuth2 you will receive an error stating Access not enabled. Ask your Everlaw Organization Admin to enable OAuth2. Once they do, you will be able to authenticate.

4. A screen asks you to authorize the Platform_read and Data_read permissions for claude.ai. Select Allow to grant the requested permission.
   
   This creates the connection between Everlaw and Claude.

You are redirected back to the Claude Connectors page. Your Everlaw connector should now say Configure rather than Connect. This indicates that the connection has been made and you're ready to get started. 
Select Chat to start using Claude to search across your Everlaw documents.

For users on projects in multiple organizations

Claude's ability to search Everlaw projects is based on the owning organization's enablement of OAuth2 in Everlaw. If you have access to projects owned by multiple organizations, you will only be able to use Claude to search the projects for which OAuth2 has been enabled at the Organization level. 

You only need to follow the steps to form the connection once. When an additional organization enables OAuth2, the projects within that organization that you have access to will immediately become searchable within Claude.

[Optional] Step 3: Allow network egress in Claude to grant full text access

With the default settings allowed by the Everlaw MCP connection, Claude has access to the search results returned by Everlaw. For example, if you ask Claude to find documents that mention "birthday," Claude will know that the returned documents contain the word "birthday," and can perform additional searches and analysis on them, but will not have access to the rest of the text within those documents by default.

For Claude to access the full underlying text of returned documents, an admin with the Owner or Primary Owner role for your team's Claude account must enable access to specific links from Everlaw. This allows Claude to access the links that contain the full text of returned documents, which then enables users to ask Claude to search and analyze across the text.

Requirements: To allow network egress and allowlist a domain, you must be the Owner or Primary Owner of your organization's Claude account. Alternatively, an Owner or Primary Owner can grant access to these settings via custom roles within Claude.

To enable the links:

1. Within your Claude enterprise account, go to Settings > Capabilities.
2. If it's not already enabled, switch on Allow network egress.
3. In the Additional allowed domains field, enter "esi-project.s3.amazonaws.com" and select Add. This allows Claude to access the links that contain the full text of returned documents.

Important: This updates the setting for all users in the enterprise organization.
 

Supplemental information: How Everlaw and Claude connect

This section provides a bit of technical background on the connection between Everlaw and Claude. It's not necessary to understand this section before using Claude to search your Everlaw documents: you can get started right away by setting up your connection and then asking questions. If you're interested in some background information on how Claude and Everlaw connect, read on.

The connection between Everlaw and Claude is formed through a Model Context Protocol (MCP). MCPs have emerged as the standard tool that software companies use to securely connect AI tools with service providers like Everlaw. The Everlaw MCP server provides a secure, standardized, and reliable connection, with defined tools that allow the Claude AI agent to search your Everlaw documents. At this time, the MCP tools that Everlaw has developed allow Claude a read-only connection to Everlaw, meaning that you cannot take actions such as modifying, exporting, or deleting documents from within Claude.

Because the MCP server is authenticated based on each individual user's Everlaw permissions, Claude's responses never share information beyond what a user has access to within Everlaw.

Once a connection to the MCP server is established, you can ask Claude your natural language questions, and Claude will then:

1. Interpret the question to identify the information it needs from Everlaw.
2. Translate the question into Everlaw Search and send the query to Everlaw through the MCP.
3. Use the information received from Everlaw to answer your question. 

Because Claude understands natural language and can synthesize across documents, your searches are not limited to pulling together a specific set of documents based on their characteristics. Instead, you can ask targeted, analytical questions to understand and draw insights from your data.

While Claude does not use the API directly, the tools it has access to mirror those of the Everlaw Search API endpoints for retrieving binders, Bates information, metadata, and text (contents) searches.  

Developers can check out our Everlaw MCP Server article, which has technical details about our MCP implementation.