Problem summary
You connect Funnel MCP in a third-party MCP client and complete the early OAuth steps, but Funnel login redirects you to a Callback URL mismatch page instead of finishing authorization.
Error message or symptoms
After you sign in or approve access, login.funnel.io shows a Callback URL mismatch page. Your MCP client never receives the OAuth callback and the connection does not complete.
Your MCP client may report that the Funnel OAuth client's allowed redirect URI list does not include your client's callback URL (for example {mcp_client_callback_url}).
When does this occur
When you connect Funnel MCP in an MCP client that is not yet registered with Funnel for OAuth callbacks
During the OAuth redirect step after you sign in to Funnel
When your MCP client uses a fixed callback URL that Funnel has not added to its allowlist
Root cause
Funnel had not registered your MCP client for OAuth with Funnel MCP. Authorization cannot finish until Funnel adds your client's callback URL to the allowlist or registers your client using its Client ID Metadata Document (CIMD).
Dynamic client self-registration is not available for Funnel MCP. Your MCP client cannot register its own OAuth client at login.funnel.io/oidc/register.
Solution
Confirm your Remote MCP server URL matches your Funnel region:
Global (default):
https://mcp.ai.funnel.io/mcpEU:
https://mcp.eu.ai.funnel.io/mcp
Copy Server URL from Connect Funnel MCP in Funnel AI full view (Data > Analyze > Funnel AI).
Contact Funnel support using one of the options below. Include your MCP server URL, MCP client name (for example
{mcp_client_name}) and the Callback URL mismatch page or full error text in every request.
Option A: Add your OAuth callback URL
Use this when your MCP client connects with Funnel's OAuth client and you need a redirect URI added to the allowlist.
Your MCP client's OAuth callback URL from your client's documentation or connection settings (for example
{mcp_client_callback_url})Your OAuth Client ID from Connect Funnel MCP (Advanced), if available
Option B: Provide CIMD details
Use this when your MCP client publishes a Client ID Metadata Document (CIMD) for OAuth instead of using Funnel's static OAuth client.
Your MCP client's CIMD URL (for example
{cimd_url})Any other CIMD details your MCP client vendor documents for third-party registration
After support confirms your callback URL or CIMD registration is complete, remove and re-add the Funnel MCP connection in your client, then complete OAuth again in a new session.