Cortellis Regulatory Intelligence MCP Server
Connecting from Microsoft Copilot Studio
This guide walks you through adding the Cortellis Regulatory Intelligence (CRI) MCP server as a tool in a Microsoft Copilot Studio agent, so your agent can answer regulatory questions with authoritative content from Cortellis.
Prerequisites
- A Clarivate account with an active Cortellis Regulatory Intelligence subscription. Each user of the agent signs in with their own Clarivate account. Without a valid subscription, authentication succeeds but the tools return an error indicating that a CRI subscription is required.
- A Microsoft Copilot Studio license and maker access to a Power Platform environment.
- Generative orchestration turned on for the agent — Copilot Studio requires it for MCP tools.
- Permission to create connections in your environment. If a Power Platform data policy restricts custom connectors, your admin must allow this one.
Connection details
Use these values when Copilot Studio asks for them:
| Server name | Cortellis Regulatory Intelligence |
|---|---|
| Server description | Searches Cortellis Regulatory Intelligence and summarizes regulatory requirements, guidance and submission procedures across countries, agencies and product types. |
| Server URL | https://api.clarivate.com/lifesciences/mcp-regulatory/mcp |
| Transport | Streamable HTTP (the only transport Copilot Studio supports; SSE is not supported) |
| Authentication | OAuth 2.0 |
| Metadata / discovery endpoint | https://api.clarivate.com/.well-known/oauth-authorization-server/lifesciences/mcp-regulatory |
| Authorization URL | https://api.clarivate.com/lifesciences/mcp-regulatory/authorize |
| Token URL template | https://api.clarivate.com/lifesciences/mcp-regulatory/token |
| Refresh URL | https://api.clarivate.com/lifesciences/mcp-regulatory/token |
| Scopes | claudeai |
| PKCE | S256 supported |
Setup Instructions
- Sign in to Microsoft Copilot Studio and open the agent you want to extend (or create a new one).
- Go to the Tools page for your agent and select Add a tool, then New tool, then Model Context Protocol. The MCP onboarding wizard opens.
- Fill in Server name, Server description and Server URL using the values in the table above. The description is what the agent orchestrator uses to decide when to call the server, so keep it accurate.
- For the authentication type, select OAuth 2.0, then choose one of:
- Dynamic discovery — the server publishes OAuth metadata at the discovery endpoint above, so Copilot Studio can read the endpoints itself. Try this first.
- Dynamic — enter the Authorization URL and Token URL template from the table above.
- Manual — enter the Authorization URL, Token URL template, Refresh URL and Scopes from the table above, plus the Client ID and Client secret issued to you by Clarivate (see step 6).
- Select Create. Copilot Studio displays a callback URL (typically
https://global.consent.azure-apim.net/redirect/...). Copy it. - Register your connector with Clarivate before creating the connection. Email [email protected] with your callback URL and the client ID your connector uses, and we will allow-list them. Copilot Studio connectors authenticate with a fixed, pre-provisioned client ID instead of registering themselves dynamically, so the CRI server rejects an unknown client ID at the authorization step. See Troubleshooting for what that failure looks like.
- Once we have confirmed the registration, on Add tool select Create a new connection, sign in with your Cortellis Regulatory Intelligence account and approve the consent screen.
- Select Add to agent. The server's tools appear on the agent's Tools page and are available to the orchestrator.
- Test the agent, for example: "Summarize FDA labeling requirements for oncology products."
Note: no Cortellis data is indexed or copied into Microsoft 365 or Power Platform. Responses are fetched from Cortellis at request time over MCP, using the signed-in user's own entitlements.
If you would rather build the connector by hand in Power Apps instead of using the wizard, Copilot Studio also accepts a custom connector defined by an OpenAPI file. The operation must target the path /mcp on https://api.clarivate.com/lifesciences/mcp-regulatory and be marked x-ms-agentic-protocol: mcp-streamable-1.0. Microsoft's documentation below includes a complete sample schema.
Microsoft documentation
- Microsoft Copilot Studio — where you build and configure the agent.
- Extend your agent with Model Context Protocol — overview and prerequisites.
- Connect your agent to an existing MCP server — the authoritative step-by-step reference for the wizard, the OAuth 2.0 fields and the custom connector alternative.
- Add MCP server tools and resources to your agent.
- Troubleshooting MCP integration.
- Generative orchestration — must be on for MCP tools to be used.
Available Tools
- Cortellis_Regulatory_Intelligence_Agent: An intelligent agent that searches Cortellis Regulatory Intelligence and summarizes regulatory requirements across countries and organizations.
Troubleshooting
- "Verify your credentials", followed by a SystemError, when creating the connection. The connector's client ID has not been allow-listed on the CRI server, so the authorization request is rejected before the login page. Complete step 6 above.
- The connection worked and later stopped authenticating. Sign out and create the connection again. If it still fails, contact support — the registration may need to be re-applied.
- Tools return an error about a required subscription. The signed-in account authenticated but has no active Cortellis Regulatory Intelligence entitlement.
- The agent never calls the tools. Confirm generative orchestration is on and that the server description explains what the server is for.
For support, please contact [email protected].
Privacy
See Clarivate's privacy notices and policies.
Terms of Service
See Clarivate's terms of service.
Looking for the ready-made connector in Microsoft 365 Copilot Chat instead? See the Microsoft Copilot Chat setup guide.