MCP server: allow redirect URIs for our MCP client (Clarant)

API
1

Hi Pipedrive team,

We’re integrating the hosted Pipedrive MCP server (https://mcp.pipedrive.ai/mcp) into Clarant, an AI assistant for sales teams. Dynamic Client Registration at https://oauth.pipedrive.com/oauth/register works for our local callback, but our hosted environments are rejected with:

{"error":"invalid_redirect_uri","error_description":"Invalid redirect URI"}

Could you please allow-list these redirect URIs for DCR?

  • https://api.clarant.ai/api/v1/mcp-connectors/pipedrive/callback (production)
  • https://uat-atg-apim.azure-api.net/api/v1/mcp-connectors/pipedrive/callback (UAT)
  • https://qa-atg-apim.azure-api.net/api/v1/mcp-connectors/pipedrive/callback (QA)

Registration request: client_name “Clarant”, grant_types authorization_code + refresh_token, response_types code, token_endpoint_auth_method client_secret_basic.
This is the same request Pipedrive handled for Blueticks here: MCP server: allow redirect URIs for our MCP client (Blueticks Agents)

Thank you!

2

Hey, the urls should be whitelisted now , can you try again ?

3

Thank you, Youssef! We’ve confirmed that dynamic client registration at oauth.pipedrive.com now successfully accepts all three redirect URIs, and the authorization flow initiates as expected.

We’ll proceed with end-to-end testing using a Pipedrive account and share an update here if we encounter any further issues.