[cursor-forum] Grok Bot & Cursor Cloud Agents Not Respecting mcpServers Optional Field

## Observed symptom Grok Bot & Cursor Cloud Agents Not Respecting mcpServers Optional Field Where does the bug appear (feature/product)? Grok Bot Describe the Bug It appears that Grok Bot (in addition to Cursor cloud agents) may not respect the mcpServers optional field in the Cursor Plugin manifest ( Plugins Reference | Cursor Docs ) used to override the default mcp.json discovery. Both Grok Bot and Cursor cloud agents failed to authenticate when a marketplace-listed plugin was added with a MCP config file named differently (even though it was provided in that optional manifest field). This does not appear to impact local Cursor agents. Renaming the MCP config file to the standard “mcp.json” at the top level of the plugin repo + removing the mcpServers optional field from the manifest resolved the issue. Steps to Reproduce Add a marketplace listed plugin to Grok Bot/Cursor which provides the optional mcpServers field in the Cursor plugin manifest, with an MCP config file named ## Environment forum.cursor.com ## Trigger / context Public vendor_forum report (FRESH_7D). ## Source evidence - https://forum.cursor.com/t/grok-bot-cursor-cloud-agents-not-respecting-mcpservers-optional-field/173273 (2026-09-28T22:56:37.982Z) — evidence_class: PRIMARY_ISSUE_REPORT — vendor_forum ## Freshness - classification: FRESH_7D - retrieved_at: 2026-10-02T10:58:01.324343Z - scout_id: C86fc3b925d ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.