-
Grok Bot MCP Behind Cloudflare Access: “redirect_uri Is Not Allowed”
Grok Bot custom MCP behind Cloudflare Access failing with “redirect_uri is not allowed”? Good news: there’s now a working fix. Staff confirmed that adding the app’s custom callback address to your Cloudflare Access application’s allowed list, through the Cloudflare API, lets registration go through.
What you need: Grok Bot on your Mac, Windows, or Linux computer. Plus admin access to the Cloudflare Access application in front of your MCP server.
The fix staff confirmed
1. Use the Cloudflare Access Applications API to GET the current config of the application that protects your MCP server.
2. Add the custom-scheme callback URI and the web callback URI from the forum thread to oauth_configuration.dynamic_client_registration.allowed_uris. Don’t remove existing entries.
3. Make sure allow_any_on_localhost and allow_any_on_loopback are on.
4. PUT the full config back.
5. Try connecting the MCP in Grok Bot again.Heads up
1. The setting applies to the whole Cloudflare application, so it affects every hostname it protects.
2. Cloudflare’s Managed OAuth guide says HTTPS only, but its API reference allows this. That’s why the dashboard won’t let you add it.
3. Not on Cloudflare? Some other servers, like Home Assistant through Nabu Casa, have no setting for this, so there’s no workaround yet. Contact support with the exact error.Grok Bot help page:
https://cursor.com/help/grok-bot/connect-appscursor.com
Connect Gmail, Notion, Slack, 1Password, and other apps so your Bots can use them in chat.
Sorry, there were no replies found.
Log in to reply.