RelativityOne MCP

The RelativityOne MCP server is designed to give AI assistants/AI clients access to RelativityOne capabilities through Model Context Protocol, an open standard for connecting AI clients to external data and services through MCP connections. 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 vendor to understand how they may use, retain, or process data.
• Elicitation support varies by client - see the Supported Vendors section for details.

Supported Vendors

The following AI vendors and clients are supported. For setup instructions for each client, follow the link in the Vendor column.

Vendor	Clients
Anthropic Claude	Claude Code, Claude.ai, Claude CoWork

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 client that supports MCP connections. For setup instructions for each vendor, see the Supported Vendors section above.

Available tools

The following sections list all available tools by category. Each tool section includes an example prompt and a summary of what it returns.

Tool	Description	Elicitation	Example prompt	Returns
Connection
relone_connection_status	Checks the RelativityOne connection and confirms which instance and identity the session is bound to.	No	Am I connected to RelativityOne? Which instance?	The instance URL, tenant GUID, auth scheme, and authenticated user identity.
Clients and Matters
relone_list_clients	Lists all clients in the RelativityOne instance.	No	Show me all clients in our environment.	Paginated list with name, number, status, and creation date.
relone_create_client	Creates a new client within the RelativityOne instance.	Yes	Create a new client called 'Wayne Enterprises'.	Artifact ID, name, number, status, and creation timestamp.
relone_edit_client	Updates an existing client's properties (name, number, status).	Yes	Rename client 1234 to 'Wayne Industries' and mark it active.	Artifact ID, name, number, status, and creation timestamp.
relone_list_matters	Lists all matters in the RelativityOne instance.	No	List all matters under the Acme Corp client.	Paginated list with name, number, status, client name, and creation date.
relone_create_matter	Creates a new matter under a specified client.	Yes	Create a matter 'Project Phoenix' under the Wayne Enterprises client.	Artifact ID, name, number, status, parent client ID, and creation timestamp.
relone_edit_matter	Updates an existing matter's properties.	Yes	Change the status of matter 5678 to inactive.	Artifact ID, name, number, status, parent client ID, and creation timestamp.
Permissions
relone_list_users	Lists users in the instance with their account details.	No	Pull a list of all active users.	Paginated list with name, email, client, user type, and access information.
relone_list_groups	Lists existing user groups in the instance.	No	What security groups exist in our tenant?	Paginated list with name, client, status, and creation date.
relone_list_workspace_groups	Lists user groups that currently have access to a specific workspace.	No	Which groups have access to workspace 1015024?	Paginated list of security groups.
relone_add_workspace_group	Grants a user group access to a specific workspace.	Yes	Give the 'Reviewers' group access to the Phoenix Review workspace.	Workspace and group artifact IDs and a status message.
relone_remove_workspace_group	Revokes a user group's access to a specific workspace.	Yes	Remove the 'Contractors' group from the Phoenix Review workspace.	Workspace and group artifact IDs and a status message.
User-Group Membership
relone_list_user_groups	Lists the security groups a given user is a member of.	No	List the security groups that the user John.Doe@domain.com is a member of.	Paginated list of security groups.
relone_add_user_to_group	Adds a user as a member of a security group.	Yes	Add John.Doe@domain.com to the 'Contractors' group.	User and group artifact IDs and a confirmation message.
relone_remove_user_from_group	Removes a user from a security group.	Yes	Remove John.Doe@domain.com from the 'Contractors' group.	User and group artifact IDs and a confirmation message.
relone_list_group_users	Lists the users that are members of a given security group.	No	List the users in the 'Contractors' group.	Paginated list with artifact ID, full name, and email.
Workspaces
relone_list_workspaces	Lists workspaces in the instance.	No	Show me all workspaces created this year.	Paginated list with name, client, matter, status, use case, and state.
relone_get_workspace	Retrieves full details about a specific workspace.	No	Get details for workspace 1015024.	Name, status, matter and client hierarchy, and timestamps.
relone_create_workspace	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.	Yes	Create a workspace called 'Phoenix Review' using the standard template.	A job handle with job ID and initial state.
relone_edit_workspace	Updates workspace properties such as name, status, and assigned matter.	Yes	Rename workspace 1015024 to 'Phoenix Review - Phase 2'. / Set workspace 1015024 to inactive.	Full workspace details including name, status, matter and client hierarchy, and timestamps.
relone_list_workspace_templates	Lists workspace templates available for creating new workspaces.	No	What workspace templates can I use for a new matter?	Paginated list with name, client, matter, status, and use case.
relone_get_workspace_create_job	Checks the status of an in-progress workspace creation job.	No	What's the status of the workspace creation job I just kicked off?	Job state, progress steps, and workspace artifact ID once complete.
relone_wait_for_workspace_create_job	Blocks until a workspace creation job completes or fails.	No	Wait until the new workspace is fully provisioned, then let me know.	Final job state and workspace artifact ID.
relone_list_object_types	Lists all object types defined in a workspace.	No	What object types exist in the Phoenix Review workspace?	Paginated list with name and artifact type ID.
relone_get_fields	Retrieves the fields defined on a specific object type.	No	Show me all fields on the Document object in workspace 1015024.	Paginated list with name, field type, and object type ID.
relone_list_choices	Lists the choices available for a single-choice or multi-choice field.	No	List all choices for the 'Responsiveness' field.	Paginated list with name and display order.
Usage Reports
relone_usage_get_metadata	Gets a list of metadata available within usage reports.	No	What metadata could I build a usage report off of?	List of all metric and origin fields.
relone_usage_list_reports	Lists usage reports that exist.	No	Show me all usage reports from the last 30 days.	A list of all existing usage reports for the tenant.
relone_usage_generate_report	Creates a new usage report.	Yes	Generate a workspace storage usage report for Q1.	Report ID, name, status, type, date range, and selected fields.
relone_usage_get_report	Retrieves metadata and status for a specific usage report.	No	Get the status of usage report 4421.	Report ID, name, status, type, date range, and fields.
relone_usage_get_report_details	Retrieves the row-level data inside a usage report.	No	Show me the detail rows from the Q1 storage report.	Paginated table data with column headers.
relone_usage_download_report	Downloads a completed usage report as a CSV file. Reports larger than 10 MB are rejected.	No	Download the Q1 storage report as a CSV.	CSV string.
relone_usage_wait_for_report	Blocks until a usage report finishes generating.	No	Wait for the Q1 report to finish, then download it.	Completed report metadata.
relone_usage_delete_report	Deletes a usage report.	Yes	Delete usage report 4421.	Report ID and confirmation message.

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.

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.

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.

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.

Data Processing Agreement

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

Privacy and Cookie Policy

To learn more about how Relativity handles personal data, please see our Privacy Policy and Cookie Policy, linked in the footer of this webpage.