Anthropic Claude

This topic describes how to set up and use Anthropic Claude with the RelativityOne MCP server.

Setting up Claude Web or Claude Desktop

Follow these 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.

Elicitation support

The MCP server supports elicitation for certain tool calls, which prompts you for confirmation or additional input before executing create, edit, or delete operations. Elicitation support varies by client - in clients that do not support it, tools will execute immediately without a confirmation prompt.

Client	Elicitation Supported	Behavior
Claude Code	Yes	Prompts for confirmation before executing.
Claude.ai	No	Executes immediately without a confirmation prompt.
Claude CoWork	No	Executes immediately without a confirmation prompt.

Elicitation support is a third-party client dependency and is subject to change. Check your client's documentation for the most current status.

Frequently asked questions

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.

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.

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.

What happens when I use an elicitation-enabled tool in Claude.ai or Claude CoWork?
Those tools will execute immediately without prompting for confirmation, since Claude.ai and Claude CoWork do not currently support elicitation. If you need the confirmation step, use Claude Code. Elicitation support is determined by the client vendor and is subject to change.

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.

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.