抄作业 / 做成了什么 / Grok Bot
Forum: remote MCP header missing on reused sessions (HTTP 400)
标题与摘要为原文，未翻译。
- 做了什么
- Developer report with a runnable reproduction that Grok Bot drops the MCP-Protocol-Version header when it reuses a remote MCP session, so strict servers return an empty HTTP 400; staff confirmed it and flagged the suggested fix.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Grok Bot Describe the Bug Full investigation, redacted server trace and runnable reproduction: Grok Bot (Cursor MCP client) omits MCP-Protocol-Version on reused sessions → empty 400 from T3 Code; analysis, repro and fixes · GitHub OAuth authorization, token exchange, MCP initialization and the first tools/list succeed. Later requests arrive with Mcp-Session-Id but without MCP-Protocol-Version. On a session negotiated as 2025-06-18, strict servers reject them with HTTP 400 and an empty body. Grok Bot shows: Streamable HTTP error: Error POSTing to
展开全文
endpoint: The requested tools never execute. Server traces prove the header is absent when requests arrive, but do not establish which connector component drops it or conclusively identify the rejected RPC method. Steps to Reproduce …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 仅为案例整理，不构成任何投资建议
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下