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

做了什么

Staff (mohitjain, 2026-09-07): For account-default shared connectors like Inkbox, the identity you authorize on desktop carries to phone—you usually don’t need the iOS Connect card. If iOS still shows “Unsupported redirect_uri” but tools work after desktop auth, skip Connect on mobile and just ask the bot to use the tool (or reopen the app). Mobile connect-flow redirect_uri bugs remain tracked sep

场景

调研监控 写代码上线

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• ✓ 截图 / 媒体有
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Grok Bot’s Inkbox MCP connect card fails before OAuth starts with: Couldn’t start sign-in: Unsupported redirect_uri Connector: Inkbox (plugin id 57102943, MCP server user-Inkbox, status needsAuth). Triggered via AuthenticateMcpServer for account=default so agents can send urgent SMS/iMessage to Holiday. Expected: sign-in / OAuth starts from the connect card. Actual: sign-in never starts; the card shows Unsupported redirect_uri with Retry. Card copy: “Give Cursor an Inkbox identity for email, SMS, iMessage, voice calls,

展开全文

contacts, n…” Steps to Reproduce • In Grok Bot, try to connect / re-authenticate the Inkbox MCP connector (plugin 57102943 / server user-Inkbox). • Observe the connect card. • Note it never opens a browser sign-in flow; it stays on Unsupported redirect_uri. Expected Behavior …

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

效果截图

提示词

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

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 会读写你的邮箱：先只给只读和草稿权限，发信前人工审批
• 用到浏览器或网页登录：最耗额度，能用 connector 就别开浏览器
• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下