MCP Registration URL missing for ChatGPT Connector

Hey ​@Lorin !

Thanks for the screenshot and feedback. The short answer is: there is no Registration URL to enter, and you can leave that field blank for our MCP server.

That field only applies to Dynamic Client Registration (DCR), where the AI assistant registers itself automatically with the server. Front doesn't support DCR by design. Instead, Front's MCP server uses a confidential OAuth connection: you create your own OAuth app in Front and give ChatGPT its Client ID and Client Secret. That's why the field never auto-populates, and why ChatGPT warns that "registration will fail" — it's expecting DCR, which we intentionally don't offer. (Your Auth URL and Token URL discovered correctly, so the rest of the config is fine.)

 

Here's the path that will work:

1. In Front, create a developer app, then in the Features tab add an OAuth feature. Note the Client ID and Client Secret.
2. In that OAuth feature, add ChatGPT's redirect/callback URL. ChatGPT shows this under Advanced settings when you set up the connector — it's typically https://chatgpt.com/connector_platform_oauth_redirect. Register exactly what ChatGPT displays.
3. Under Feature Access, enable only "MCP Server" (enabling other feature types can cause 403s during authorization), and select the resource permissions you want the agent to have: read, write, and/or send.
4. Back in ChatGPT, leave Registration URL blank. Open Advanced OAuth settings and enter the Client ID and Client Secret from step 1. Leave the Auth URL and Token URL as discovered.
5. Save and complete the OAuth sign-in. Each user authorizes individually, and the agent inherits that user's Front permissions.


Tell me if this is useful! Thanks again

Thanks Martin!

I got all the way to Step 5, but I’m now getting this Error in ChatGPT when trying to ‘connect’ the App to my account. *ChatGPT's redirect/callback URL was not shown to me in the Advanced Settings, so I used the URL that you said was typical: https://chatgpt.com/connector_platform_oauth_redirect

When trying to connect my Chat GPT account to the Front App/Connector that I just created, I get this error message. 

Front Settings:

Hmmm

Your screenshot rules out the two things — only "MCP Server" is enabled at Front, and the redirect URL looks right. A few things can cause "403: Unauthorized client," so let's work through them in order:

1. Confirm the exact redirect URI. On the Front error page, copy the full URL from the address bar, find the redirect_uri= value (decode %3A to ":" and %2F to "/"), and make sure that exact string is registered under Redirect URLs. It has to match character-for-character.
2. Enable Namespace access. Section 3 currently has all three boxes unchecked, so the app is granted no data. Check Global, Shared, and Private resources (the token is still capped by your own Front permissions, so this is safe).
3. Align scopes. Send and Delete are unchecked in Resource permissions. If ChatGPT requests them by default, the flow can error — either enable them or leave as-is and retry.
 

Save after each change and retry the connection. If it still fails, send me the full address-bar URL (redact the client_id) and I'll pinpoint it.

Best,

Hi Martin, I’m running into a related issue with ChatGPT Business, but I’m not getting as far as the Front authorization screen.

I followed the steps you provided:

• Created the OAuth app in Front
• Enabled only MCP Server
• Added the exact callback URL displayed by ChatGPT
• Entered the Front Client ID and Client Secret
• Used client_secret_basic
• Requested feature:mcp, read, and write
• Enabled Global, Shared, and Private namespace access
• Left Send and Delete disabled

In ChatGPT, the setup screen only displays Create. It never opens the Front OAuth authorization page or shows a tool-scanning step.

The app is created, but it then shows:

“No actions are available for this app.”

Because it has zero actions, the workspace Enable button is greyed out, and refreshing the actions does not discover anything.

I tested in both Chrome and Brave with pop-ups allowed. This is on a ChatGPT Business workspace.

Is this a known issue with the current ChatGPT Business connector flow, or is there another step required to trigger Front OAuth and action discovery?

Thanks!

Hi ​@Lorin,

Have you been able to reach out to OpenAI regarding this issue? I’m wondering whether they can advise you on how to connect a confidential OAuth connection versus one that expects Dynamic Client Registration. 

​@Erick SGY I’d also suggest reaching out to OpenAI if you can. My understanding is that ChatGPT Business’ MCP support is still in beta. Your issue might be related to developer mode, but the Open AI team would know best. MCP server might still require developer mode to complete OAuth and discover tools on ChatGPT Business.

1. Ask your workspace admin to enable Developer Mode (Settings → Connectors → Advanced → Developer mode). 
2. Once developer mode is on, retry the connector setup. You should see the OAuth prompt and tool discovery step you're expecting.
    

​@Lorin ​@Erick SGY Getting an official diagnosis from OpenAI would help accelerate a solution from their end or a clear indication of what we can change on Front’s end to facilitate the setup.

Thanks!