CircleCI supports OAuth 2.0 Dynamic Client Registration (DCR) with PKCE for API / MCP auth. The limitation is redirect URIs: DCR only accepts RFC 8252 loopback (localhost / 127.0.0.1 / ::1) plus a small allowlist of hosted callbacks (e.g. VS Code, Claude, Cursor Cloud Agents).
Cloud / remote agent platforms
We need either expanded allowlisting of trusted hosted OAuth callbacks for cloud / remote agent platforms, or another supported OAuth path for those hosts.
Priority platforms that fail (or previously failed) with "no supported redirect_uri":
Without this, those hosts cannot complete OAuth and must fall back to a Personal API Token / API-key connector.
Enterprise MCP gateways
Enterprise customers also need to put the CircleCI hosted MCP server (https://mcp.circleci.com/v1/mcp) behind their own MCP / AI gateway (for example Cloudflare Zero Trust MCP Server Portals, LiteLLM, or similar). Those gateways broker OAuth for every user and register a non-loopback HTTPS callback. Open DCR rejects those callbacks with invalid_redirect_uri. Expanding open DCR to shared multi-tenant proxy domains is a security concern, so one-off allowlisting of shared gateway URLs is not a complete answer.
Enterprise customers are asking for:
  1. Classic / organization-registered OAuth clients — a client_id (and client credentials where needed) with redirect URIs bound to that customer's gateway, that they can configure in the gateway.
  2. Optionally, a secure self-serve way for an organization to register its own known hosted callbacks without putting shared proxy domains on open DCR.
Workarounds such as personal API tokens or connecting an IDE directly to mcp.circleci.com often do not meet enterprise security or central gateway-control requirements, so they are not a substitute for the enterprise ask above.