常驻用量

抄作业 / 做成了什么 / Grok Bot

Custom MCP OAuth DCR: cursor:// callback breaks Cloudflare https-only allowlists

标题与摘要为原文,未翻译。

做了什么
Staff (deanrie, 2026-09-16): Dynamic Client Registration sends three redirect_uris—cursor://anysphere.cursor-mcp/oauth/callback, https://www.cursor.com/agents/mcp/oauth/callback, and http://localhost:8787/callback; Grok Bot desktop uses localhost, but Cloudflare Managed OAuth rejects the whole set because it can’t allowlist cursor://—tracked server-side fix to drop non-https callbacks.
场景
调研监控
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体来源未提供
  • 步骤 / 章节来源未提供
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

— 表示来源没有给出,本站不补写。

来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Custom remote MCP OAuth fails before sign-in with: redirect_uri is not allowed by the account configuration. Existing connector Owner Google Tasks MCP remains needsAuth / authentication_required, tools=0. Endpoint: Sign in ・ Cloudflare Access . The server uses Streamable HTTP protected by Cloudflare Access Managed OAuth. Bot diagnostics do not expose the DCR redirect_uris array. Steps to Reproduce • Add the remote MCP through Grok Bot. • Request OAuth authorization on that existing connector. • Registration fails with the
展开全文 redirect_uri error before the sign-in card opens. • Allowlisting the exact /agents/ and then /bot/ callbacks in Cloudflare did not resolve it. No duplicate connector was added; retries have stopped. Expected Behavior OAuth should open the owner sign-in flow, then load MCP tools. …
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

摘自论坛首帖,照录原文,未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制
  1. 读原文:forum.cursor.com ↗
  2. 把原文里的步骤/提示词整理成一条消息交给 Bot
  3. 先手动跑一次,再决定频率
风险与限制
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下