Grok Bot & Cursor Cloud Agents Not Respecting mcpServers Optional Field

Support Bug Reports
, , ,
1

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 something other than “mcp.json”.

Attempt to authenticate from Grok Bot or a Cursor cloud agent.

Operating System

MacOS

Version Information

Grok Bot v0.61.0
Cursor v3.22.12

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @bjohnson1,

The mcpServers manifest field is supported by both Grok Bot and cloud agents, so your original layout was fine and there’s no need to keep the rename. What actually tripped it up was a step during plugin install that intermittently failed to register the connector, so there was nothing to sign in to. That’s on our side, not your setup, and it’s an issue we’ve been tracking and improving.

If a plugin ever shows as installed but never offers a sign-in, remove it and re-add after a few minutes. Is it working now for you in both Grok Bot and cloud agents?

7

Hey Mohit,

Understood! And thanks for getting back so quick! It’s working now.

Best,

Bailey