Skip to main content

MCP Setup and Administration

How To Setup and Administer IPRally Enterprise MCP Access

Written by JP - John Paul Keeler

Setup for enterprise IT-managed environments

Enterprise administrators can enable IPRally MCP for all licensed users in their organisation through a single integration, so individual users don't need to configure anything themselves.

There are two paths depending on what your AI platform supports:

Applications that support Dynamic Client Registration

Most modern AI platforms (ChatGPT, Claude) support Dynamic Client Registration (DCR). Your IT team can add IPRally as a connector using just the server URL, with no pre-shared credentials needed. The client registers itself automatically on first connection.

Configure this in your organisation's admin console for the relevant AI platform. All users with active IPRally licences will then have access.

Note: The Copilot Studio, which adds Agents and custom tools to Microsoft 365 Copilot, has misconfigured dynamic discovery and does not comply with the MCP spec. Instructions to add a custom tool in Copilot Studio are available here.

Applications that require pre-registered credentials

Some enterprise platforms, notably Gemini Enterprise, do not support Dynamic Client Registration. For these, your IT team will need a client ID and client secret issued by IPRally.

To get started:

  1. Contact IPRally at support@iprally.com (or your account manager)

  2. We will provision a client ID and secret for your organisation

  3. Your IT team configures the integration using these credentials and the server URL

  4. All users with IPRally licences in your tenant will have access

Gemini Enterprise

  1. Open Data Stores > Sources > Custom MCP

  2. Add the details received from support@iprally.com.

  3. Open Data Stores > <The custom MCP added> > Actions and enable the tools.

Security and data handling

  • Read-only access to the shared patent corpus. No workspace data, no write operations.

  • Your existing IPRally identity, authenticated via Auth0 with OAuth 2.1 + PKCE. No separate credentials.

  • Audience-bound tokens. Access tokens are scoped to the MCP server and cannot be used against other IPRally services.

  • No customer data used for training, consistent with IPRally's existing data handling commitments (ISO 27001, GDPR).

For a full technical and security description, see the IPRally Search MCP Technical Overview.

Troubleshooting

Authentication fails or loops

Clear your browser cookies for login.iprally.com, then try connecting again. If using Claude Code, run claude mcp remove iprally and re-add.

"Unauthorized" or MCP errors after initial setup

Your IPRally session may have expired. “Reconnect” the IPRally MCP integration from your application setting to re-authenticate.

"Oops, something went wrong" on login

This error appears when your application hasn't been registered with IPRally yet. We monitor these attempts and register new applications as they appear, but if the error persists, contact support@iprally.com with the name of the application you're using and we will enable it for you.

Your application isn't listed

Any MCP-compatible application can connect to IPRally. Use the server URL https://mcp.iprally.com/mcp as a custom/remote MCP server. If your application doesn't support Dynamic Client Registration, contact us for a client ID and secret.

Questions?

Reach out to your IPRally account manager or email support@iprally.com.

Did this answer your question?