Skip to main content

How to Set Up Juristat MCP Server in Claude

This guide walks you through connecting the Juristat MCP server to Claude. The whole process takes about two minutes.

T
Written by Tasnim Islam

What You Need Before You Start

  • A Claude Pro, Max, Team, or Enterprise account (custom connectors are not available on the free plan)

  • OAuth credentials (Client ID and Client Secret) from your Juristat account team

Table of Contents

Admin Setup

Reference

Don't have MCP enabled? Contact sales@juristat.com for more information

Running into errors or unexpected behavior? Reach out to support@juristat.com.


Step 1: Add the Juristat Connector

In Claude, go to Settings > Connectors (on Team or Enterprise plans, this may be under Organization Settings > Connectors). Scroll to the bottom and click Add custom connector.

In the dialog that appears, enter the following:

Click Advanced settings to expand the OAuth fields and enter the credentials Juristat provided:

  • OAuth Client ID: Enter the Client ID from Juristat

  • OAuth Client Secret: Enter the Client Secret from Juristat

You can find the 0Auth credentials by:

  • Logging into your Juristat Account β†’ Settings β†’ MCP Tab

Click Add. Claude will connect to the Juristat MCP server and discover the available tools. You may be prompted to sign in with your Juristat credentials to authorize the connection.

If you are not prompted automatically, go to Settings > Connectors, find Juristat, and click Connect. You will be asked to grant profile and offline access. This keeps your session active so you do not need to sign in each time.


Step 2: Set Tools to Always Allow (Recommended)

By default, Claude will ask for your approval before calling any Juristat tool. To skip those prompts and have Juristat tools run without interruption, set the connector to Always Allow.

Go to Settings > Connectors, find Juristat MCP Prod, and click Configure. At the top of the tool list, open the dropdown next to Other tools and select Always allow. This applies to all 18 Juristat tools and means Claude will call them without asking for confirmation each time.

You can also control individual tools from this screen if you want to allow some and block others.


Step 3: Use Juristat in a Conversation

Start a new chat. Click the + button in the message composer (or type **/), select Connectors, and enable Juristat for the conversation. You can now ask questions in natural language and Claude will call the appropriate Juristat tools.

Try a query to confirm the connection is working:

  • "Get me the art unit report for art unit 2100."

  • "Search for recent patent applications filed by Microsoft."

  • "I just received an office action on application 16/123,456. Study the examiner's tendencies on similar office actions and advise me how to proceed."


Where It Works

Once you add the connector via claude.ai, it is available across all Claude clients automatically:

  • Claude web app (claude.ai)

  • Claude Desktop app (macOS and Windows)

  • Claude mobile apps (iOS and Android)

You do not need to configure the connector separately in each client.


Publishing to your Organization

On Team and Enterprise plans, a workspace Owner can add the Juristat connector at the organization level. The Owner is the only person who needs the MCP server URL, Client ID, and Client Secret. Once added, the connector appears in every user's Settings > Connectors list automatically.

Each user still needs to click Connect once and sign in with their own Juristat credentials to authorize their session. They do not need to configure any server details themselves.

Owners can manage which tool calls are allowed or restricted across the organization from Organization Settings > Connectors.


Support

Resource

Link / Contact

Juristat Support

support@juristat.com or your account manager

Claude Connectors

support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Building MCP Connectors

support.claude.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers

Did this answer your question?