Support Custom Domains for CIPP MCP Connections
A
Andrew Olsen
Improve the CIPP MCP connector setup to fully support custom CIPP domains and more reliable OAuth callback handling. Users reported that connections only succeed when using the CIPP-generated connector URL instead of a custom domain, even when the custom domain is configured correctly. The setup process also produced conflicting guidance about whether the callback URL should be registered under Web or Mobile and desktop redirect URIs in Azure. Additional issues included unreliable behavior when multiple MCP-allowed API clients are enabled and the optional API client ID field not functioning consistently. The request is to support custom domains for MCP connections, clarify and standardize OAuth callback requirements, and improve compatibility when multiple API clients are configured.