Hello Intercom team,
we would like to connect Intercom's MCP server to ChatGate (https://chatgate.ai), an AI assistant platform where people connect their own tools so their agent can work across them. Dynamic client registration currently answers "Redirect URI https://chatgate.ai/api/connectors/intercom/callback is not in the allowlist, reach out to Intercom Customer Support if you believe we should support it." — so here we are.
Product: ChatGate (client_name "ChatGate", client_uri https://chatgate.ai)
MCP endpoint: https://mcp.intercom.com/mcp (US). If you allowlist EU separately, please include the same redirect URI for https://mcp.eu.intercom.com as well.
Production redirect URI: https://chatgate.ai/api/connectors/intercom/callback
Client details: public client (token_endpoint_auth_method "none"), grant_types authorization_code and refresh_token, PKCE with S256. Our registration attempt: POST https://mcp.intercom.com/register returned HTTP 400 with error "invalid_redirect_uri".
Use case: each ChatGate user connects their own Intercom workspace through OAuth, so their AI assistant can look up conversations, contacts and help center content when that person asks. Tokens are stored encrypted, per user.
If you do not add redirect URIs to an allowlist, please tell us the official way to register a public client for this callback instead.
Contact: yangyuejun@muse.ai
Thank you!