---
title: "Connect custom MCP Clients"
slug: "connect-a-custom-application"
updated: 2026-06-02T10:37:11Z
published: 2026-06-03T07:30:00Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pigment.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect custom MCP Clients

To connect AI systems not listed in [Connect common MCP Clients](/v1/docs/connect-common-mcp-clients) to Pigment’s MCP Server, follow the below instructions.

> [!WARNING]
> ⚠️ Important
> 
> Your custom MCP client must support **OAuth 2.1 with Dynamic Client Registration (DCR)**. API keys and other authentication methods are not supported.

1. **Get the client's callback URL.**Check your MCP client's documentation for its OAuth callback URL. If it's not listed, attempt to connect - the authentication flow will fail and return an error message containing the callback URL: `No MCP connector type found for redirect uris ["https://example.com/oauth/callback"]` . The callback URL is the one shown in brackets.
2. **Register the client in Pigment.**Go to **Workspace Settings > Integrations > MCP** and add a new MCP client using the callback URL. Two whitelisting options are available:
  - **Static URL:**whitelist a fixed callback URL with an exact path (e.g. `https://example.com/oauth/callback` )
  - **Dynamic URL:** whitelist all URLs beginning with a specific path (e.g. `https://example.com/oauth/callback/*` will match any URL starting with `https://example.com/oauth/callback`).