Connect Microsoft Copilot Studio to the Collibra MCP

August 31, 2026

Microsoft Copilot Studio connects to the Collibra MCP server through a custom connector configured with OAuth 2.0. After you connect, your Copilot Studio agents can use Collibra's governed metadata tools directly. The recommended approach is for an administrator to create the connection once and share it with selected user groups.

Note The Collibra MCP server runs in the Collibra Cloud environment, so this integration is not available for Collibra Platform for Government or Collibra Platform Self-Hosted (CPSH).

Prerequisites

In your Collibra environment

You need admin privileges in Collibra to register an OAuth application.

In your Microsoft Copilot Studio environment

You can create custom connectors and agents in your Copilot Studio environment.

You configure this connection in three stages due to a dependency between the two systems: Collibra requires a redirect URI to register an OAuth application, but Copilot Studio does not generate its redirect URI until it has a Client ID and Secret from that application. Start in Collibra with a placeholder redirect URI to get those credentials, use them to create the connector in Copilot Studio, then return to Collibra to swap in the real redirect URI.

Step 1: Register an OAuth application in Collibra

This step requires admin privileges in Collibra.

Go to Settings.
Click OAuth applications.
Click New Application.
Click Register user application.
Enter an application name.
Enter https://localhost as a placeholder redirect URI. You update this with the real value in Step 3, once Copilot Studio generates it.
Deactivate Enable Proof Key for Code Exchange (PKCE).

Important Microsoft Copilot Studio's connector does not support PKCE (RFC 7636). If you leave PKCE active, authentication fails with an invalid_request error for the missing code_challenge parameter.
Click Register.
Copy the OAuth Client ID and Client Secret. You need them to configure the connector in Microsoft Copilot Studio.

Step 2: Create the MCP connector tool in Microsoft Copilot Studio

Go to https://copilotstudio.microsoft.com/environments/<environment_id>/tools.
Click New tool and select Model Context Protocol.
Select OAuth 2.0 for authentication and select Manual as the type.

Enter the connector details:

Field	Value
Server Name	The name of your server.
Server Description	The description of your server.
Server URL	`https://<tenant>.collibra.com/rest/mcp`
Authentication	OAuth 2.0, Manual
Client ID	Client ID from Step 1.
Client Secret	Client Secret from Step 1.
Authorization URL	`https://<tenant>.collibra.com/rest/oauth/v2/authorize`
Token URL	`https://<tenant>.collibra.com/rest/oauth/v2/token`
Refresh URL	`https://<tenant>.collibra.com/rest/oauth/v2/token`
Scopes	Leave empty. Collibra accepts an empty scope or `offline_access`, but neither is required.

Save the connector.

Copilot Studio generates a redirect URL on the connector's Security tab.

Step 3: Update the OAuth application in Collibra

In Microsoft Copilot Studio, open the connector tool you created.
Go to the Security tab and copy the redirect URL.
In Collibra, go to Settings > OAuth applications and edit the application from Step 1.
Replace https://localhost with the copied redirect URL.
Important Keep PKCE deactivated when you edit the application.
Save the application.

Use the connection

In Microsoft Copilot Studio, go to Agents.
Create a blank agent, or open an existing one, and wait until Copilot Studio confirms the agent is provisioned.
Go to the Tools tab and click Add tool.
Click Model Context Protocol and select your MCP connector.
Click Not connected, click Create new connection, and click Create.
Sign in with your Collibra credentials in the OAuth prompt.

Your agent connects to the Collibra MCP.

Confirm the connection by prompting your agent to list all tools available through the connected MCP connector. If Collibra MCP tools appear in the response, your connection is ready for use.