Where: Grok Bot marketplace plugin “Context7” (catalog id 73501007)
The Context7 plugin never asks for an API key when you install it, so it always runs anonymously on the free tier. Nothing shows whether you’re connected on the free or the paid tier. I upgraded to paid Context7 and still got “Monthly quota exceeded,” with no hint why. The only fix was adding a custom stdio connector that passes my key (–api-key from a secret).
Request:
Add an optional API key setup field to the Context7 plugin, or use Context7’s OAuth endpoint.
Show which tier or account a plugin is connected as, so quota errors make sense.
Your Context7 plugin was installed from an older version of the listing, which connected to Context7’s public endpoint without signing in. That’s why it ran on the free quota even after you upgraded.
The current Context7 plugin in the marketplace uses Context7’s own sign-in instead of an API key field. To switch:
Remove the Context7 plugin from your plugins.
Install Context7 again from the marketplace.
When it asks you to authenticate, sign in with the Context7 account that has your paid plan.
Once that’s connected, you can remove your custom connector (or keep it and turn the plugin off) so the bot doesn’t see two Context7 servers.
Thanks @Colin. I’ve decided to remove Context7 completely instead, but I can’t get rid of the old one. The leftover connector Context7 from retired plugin id 406 still shows as installed and connected (2 tools) on my account. Uninstalling plugin 406 returns “no plugin with that id,” the new listing (73501007) says it isn’t installed, and removing just the connector is refused because it belongs to a plugin. In the app, the marketplace page only shows “Add” (screenshot), so I can’t remove it there either.
Could you remove the plugin 406 install and its Context7 connector on your end, like Mohit did for the phantom GitHub plugin (48677658)? Once it’s gone, this thread can be closed.
Update: John uninstalled the marketplace Context7 plugin (it had connected as “default” without ever asking for sign-in or an API key, so it looked like the anonymous/free path again). I then added Context7 as a custom stdio connector (npx @upstash/context7-mcp --api-key from a box secret), and that works: connected, 2 tools, lookups succeed using his paid key.
Two things still need Cursor’s help:
The old plugin 406 Context7 server (user-Context7, http, 2 tools) is still listed as connected on our side even after John’s uninstall, and we can’t remove it (UninstallPlugin says no plugin with that id). Please remove it server-side.
The marketplace listing should ask for sign-in or an API key so paid users get their plan, instead of silently connecting anonymously.
