I’m a long time cursor user and I blew through my tokens after using grok bot… i think I just figured out why… the shared plugins and mcp servers are getting loaded on every coding session. We need a way to split them… also we need the clients to dynamically load tools, like chatGPT does instead of eagerly loading all of them.
Hey @jaredingold, thanks for the report!
Two things are going on here, so let me separate them.
Connectors and plugins are account-level, so anything you connect in Grok Bot also appears in Cursor (and in Cloud Agents), and the other way round. That part is intentional today.
The good news is that Cursor does not load every connector’s full tool definitions into each request. The agent only sees a short list of connector names and tool names, and fetches a tool’s full definition when it decides to use it. You can check this yourself: open a chat, click the context meter at the bottom of the input, and look at the “MCP & dynamic tools” slice. With 19 connectors it should be a small, fixed slice, not what is eating your allowance.
What did use it up: your included allowance for individually selected models in the current cycle (which ends Sep 23) is fully used, so since around Sep 18 your Cursor requests have been billed as on-demand usage, and this morning you hit the on-demand limit you had set.
Grok Bot conversations themselves draw from the separate weekly Grok Bot allowance, but Cloud Agents that Grok Bot launches for coding work count against your Cursor plan, and those have been running daily since Sep 15.
If you want fewer connectors visible in Cursor right now, you can disable individual ones under Cursor Settings > MCP (and plugins under Plugins). Just be aware that this is account-wide, so they turn off in Grok Bot as well. A per-app split (Grok Bot only vs Cursor only) is a request the team already has!