RelativityOne MCP

The RelativityOne MCP server is designed to give AI assistants access to RelativityOne capabilities through Model Context Protocol, an open standard for connecting AI tools to external data and services through MCP clients. As a system administrator, you can use it to perform day-to-day tasks such as managing matters, configuring workspaces, granting access, and reviewing system usage.

Considerations

• The MCP server acts as the signed-in user. It performs every action on their behalf and the action is recorded under their identity.
• Relativity Audit captures actions taken through the MCP server and attributes it to the user who authenticated the connection.
• To perform actions through the MCP server, the authenticated user must be a System Administrator and have the granular permissions required for each operation.
  • Due to the System Administrator requirement, it is not currently possible to give specific users within a client domain access to this capability.
• Review your agreement with your AI assistant provider (for example, Anthropic) to understand how the assistant may use, retain, or process the data it accesses.
• The MCP server supports elicitation for certain tool calls. Only MCP clients that also support elicitation, such as Claude Code, can use this feature.

Setup

Prerequisites

Before you enable the MCP connection, confirm that you have the following:

• A RelativityOne instance with the instance MCP server enabled by Relativity Support.
• The OAuth Client ID provided by Relativity Support when your instance was configured for MCP.
• You must be a System Administrator in the RelativityOne instance.
• The required RelativityOne permissions per tool (Usage reports tools require extra permissions, for example).
• An AI assistant such as Claude Web or Desktop.

Setting up Claude Web or Claude Desktop

Use the following steps to connect Claude to your RelativityOne instance.

1. Open Claude and sign in.
2. Go to Settings.
3. Go to Connectors.
4. Select Browse Connectors.
5. Search for Relativity and then select it.
6. Press Connect.
7. Paste your RelativityOne Server URL with /mcp appended to the end (for example, https://[YourTenantHostname].relativity.one/mcp). To find your tenant hostname, look at the first part of the web address in your browser after you sign in to RelativityOne.
   1. If your tenant hostname is https://kcura.relativity.one/ for example, the Server URL to enter would be https://kcura.relativity.one/mcp.
8. Paste the OAuth Client ID provided by Relativity into the OAuth Client ID field (you should have received this key from Relativity when your environment was enabled for MCP).
9. Click Continue.
10. Authenticate with the RelativityOne instance.
11. Confirm that the RelativityOne connector is toggled on and available in Claude before starting to chat.

Available tools

The following table lists the tools installed with the MCP plugin and shows example prompts for each tool.

Category	Tool	Supports Elicitation	Description	Example Prompt
Connection	relone_connection_status		Checks the RelativityOne connection and confirms which instance and identity the session is bound to.	Am I connected to RelativityOne? Which instance?
Clients & Matters	relone_list_clients		Lists all clients in the RelativityOne instance.	Show me all clients in our environment.
Clients & Matters	relone_create_client	Yes	Creates a new client within the RelativityOne instance.	Create a new client called 'Wayne Enterprises'.
Clients & Matters	relone_edit_client	Yes	Updates an existing client's properties (name, number, status).	Rename client 1234 to 'Wayne Industries' and mark it active.
Clients & Matters	relone_list_matters		Lists all matters in the RelativityOne instance.	List all matters under the Acme Corp client.
Clients & Matters	relone_create_matter	Yes	Creates a new matter under a specified client.	Create a matter 'Project Phoenix' under the Wayne Enterprises client.
Clients & Matters	relone_edit_matter	Yes	Updates an existing matter's properties.	Change the status of matter 5678 to inactive.
Permissions	relone_list_users		Lists users in the instance with their account details.	Pull a list of all active users.
Permissions	relone_list_groups		Lists existing user groups in the instance.	What security groups exist in our tenant?
Permissions	relone_list_workspace_groups		Lists user groups that currently have access to a specific workspace.	Which groups have access to workspace 1015024?
Permissions	relone_add_workspace_group	Yes	Grants a user group access to a specific workspace.	Give the 'Reviewers' group access to the Phoenix Review workspace.
Permissions	relone_remove_workspace_group	Yes	Revokes a user group's access to a specific workspace.	Remove the 'Contractors' group from the Phoenix Review workspace.
User-Group Membership	relone_list_user_groups		List the security groups a given user is a member of	List the security groups that the user John.Doe@domain.com is a member of
User-Group Membership	relone_add_user_to_group	Yes	Add a user as a member of a security group	Add John.Doe@domain.com to the 'Contractors' group
User-Group Membership	relone_remove_user_from_group	Yes	Remove a user from a security group	Remove John.Doe@domain.com from the 'Contractors' group
User-Group Membership	relone_list_group_users		List the users that are members of a given security group	List the users in the 'Contractors' group
Workspaces	relone_list_workspaces		Lists workspaces in the instance.	Show me all workspaces created this year.
Workspaces	relone_get_workspace		Retrieves full details about a specific workspace.	Get details for workspace 1015024.
Workspaces	relone_create_workspace	Yes	Creates a new workspace from a workspace template. This call can block for 5–10 minutes with a 15-minute timeout. Do not retry or cancel during this time. Use relone_list_workspaces with the workspace name to check whether it was created.	Create a workspace called 'Phoenix Review' using the standard template.
Workspaces	relone_edit_workspace	Yes	Updates workspace properties such as name, status, and assigned matter.	Rename workspace 1015024 to 'Phoenix Review - Phase 2'. / Set workspace 1015024 to inactive.
Workspaces	relone_list_workspace_templates		Lists workspace templates available for creating new workspaces.	What workspace templates can I use for a new matter?
Workspaces	relone_get_workspace_create_job		Checks the status of an in-progress workspace creation job.	What's the status of the workspace creation job I just kicked off?
Workspaces	relone_wait_for_workspace_create_job		Blocks until a workspace creation job completes or fails.	Wait until the new workspace is fully provisioned, then let me know.
Workspaces	relone_list_object_types		Lists all object types defined in a workspace.	What object types exist in the Phoenix Review workspace?
Workspaces	relone_get_fields		Retrieves the fields defined on a specific object type.	Show me all fields on the Document object in workspace 1015024.
Workspaces	relone_list_choices		Lists the choices available for a single-choice or multi-choice field.	List all choices for the 'Responsiveness' field.
Usage reports	relone_usage_get_metadata		Gets a list of metadata available within usage reports.	What metadata could I build a usage report off of?
Usage reports	relone_usage_list_reports		Lists usage reports that exist.	Show me all usage reports from the last 30 days.
Usage reports	relone_usage_generate_report	Yes	Creates a new usage report.	Generate a workspace storage usage report for Q1.
Usage reports	relone_usage_get_report		Retrieves metadata and status for a specific usage report.	Get the status of usage report 4421.
Usage reports	relone_usage_get_report_details		Retrieves the row-level data inside a usage report.	Show me the detail rows from the Q1 storage report.
Usage reports	relone_usage_download_report		Downloads a completed usage report as a CSV file. Reports larger than 10 MB are rejected.	Download the Q1 storage report as a CSV.
Usage reports	relone_usage_wait_for_report		Blocks until a usage report finishes generating.	Wait for the Q1 report to finish, then download it.
Usage reports	relone_usage_delete_report	Yes	Deletes a usage report.	Delete usage report 4421.

Cross-tool prompts

An AI assistant can chain multiple tool calls to complete tasks that span tools. The following prompts show examples that may invoke more than one tool call.

• Create client [enter Client Name], then create a matter [enter Matter Name] for them.
• What external users exist in my system and what workspaces do they have access to?

How prompts translate to tool calls

The AI assistant chooses tools based on the tool names and descriptions that the MCP client provides, together with your prompt.

Frequently asked questions

How does authentication work?
Authentication uses OAuth 2.0 and flows through your existing RelativityOne login. When you connect Claude, you are redirected to a standard Relativity sign-in screen — Claude never handles your password or credentials. Your identity is passed through to RelativityOne, so every action taken through the MCP server is attributed to your account, exactly as if you had performed it in the User Interface.

How can I control which administrators in my instance can use the MCP server?
When Relativity enables your instance, you receive an OAuth Client ID. Only administrators you share that Client ID with can authenticate to the MCP server. Anyone without the Client ID cannot connect.

Is there a limit on how many administrators can use the MCP server at the same time?
There is no hard cap on the number of administrators using the MCP server concurrently. Rate limiting and back-off logic apply at the user level to help protect RelativityOne infrastructure.

Do I need to be a Claude administrator to add the RelativityOne connector?
It depends on how your organization has configured Claude. Some Claude administrators allow anyone to add connectors; others require approval. If your organization requires approval, request the connector and ask your Claude administrator to approve it before you install it.

Does enabling the MCP server require any infrastructure on my end?
No. The MCP server is a multi-tenant cloud service. Relativity enables your tenant on the Relativity side, and you do not need to install or manage anything on your end.

Can I use the MCP server from the Claude mobile app?
Yes. As long as you can authenticate to RelativityOne, you can use the Claude iOS or Android app to send prompts and take actions through the MCP server, provided your organization permits Claude on mobile devices.

Where does the MCP server run?
The MCP server runs in the same region as your RelativityOne instance. After data leaves the MCP server and enters Claude, it moves to wherever Claude is deployed. Factor this into your data governance considerations.

Can I connect the MCP server to multiple RelativityOne instances?
You can add multiple custom connectors in Claude, one per tenant URL, and name each distinctly. This configuration is not officially supported. Claude has been observed to retrieve data from the wrong instance under some conditions, so use this configuration with caution and share any feedback with Relativity Support.

Which Claude account type should my users connect with?
The key consideration is free vs. paid Claude accounts. Free Claude accounts may use conversation data for model training by default. Paid accounts apply contractual training restrictions and may offer additional options such as zero-day retention depending on your plan. When you authenticate the MCP server, you grant a third party access to your RelativityOne instance. Review your Anthropic agreement to confirm it reflects the governance standards your organization requires. The MCP server does not enforce a specific Claude account type, so establish internal policies for which account types your administrators may use.

Which Claude model should I use?
For workflows that benefit from advanced reasoning, use the latest reasoning model, currently Claude Opus. Claude Sonnet is also an option. Test both with your workflows to find the balance of quality and cost that fits your use cases.

Can I use the MCP server with Claude CoWork or scheduled jobs?
The MCP server works with Claude.ai, Claude Code, and Claude CoWork. Claude CoWork supports scheduled jobs, artifacts that pull and update RelativityOne data, and automated workflows. Claude Code supports custom code that integrates the MCP server with other systems.

Can I use Claude skills to enforce naming conventions or workspace standards?
Yes. You can build a Claude skill that defines workspace name formats, matter ID conventions, required checks before workspace creation, or notifications to other systems after creation. Building your own skill on top of the MCP server tools is the recommended path.

Can I ask Claude what it can do with RelativityOne?
Yes. Claude has visibility into the tools the MCP server exposes. Ask questions such as What RelativityOne tools do you have access to? or Can you do [some action] in RelativityOne? and Claude responds with the actions currently available to it.

Do I need prompt engineering skills to use the MCP server?
No. You can describe what you want in plain language. Claude structures the request, asks for missing information, and flags inconsistencies before taking action.

Does toggling off the RelativityOne connector save context tokens?
Yes. With always load tools enabled, Claude loads every RelativityOne tool into your context window at the start of each session. To reduce token usage, set the connector to load tools when needed so Claude loads them only when relevant, or toggle the connector off entirely for sessions that do not involve RelativityOne.

Data Processing Agreement

Review your Relativity agreement for details on data processing, along with the terms of your agreement with Anthropic.

Privacy and Cookie Policy

Review your Relativity agreement for details on Relativity's privacy and cookie policies, along with the terms of your agreement with Anthropic.