Grok Bot template
The connector hack - one Composio MCP gives your bot 1,000+ tools
Corey Ganim's workaround for Grok Bot's thinner connector catalog: connect the Composio connector once, then connect any of Composio's 1,000+ integrations through it - your bot uses all of them via Composio MCP. Unsponsored, in his words the easiest way to reach tools that have no native Cursor…
The prompt
Paste this into a new Grok Bot and let it set itself up.
I've connected Composio to you as an MCP connector - it is our bridge to every tool that has no native connector here. In my Composio account I enable the specific integrations we use; you reach all of them through this one connection.
How to work with it:
1. Start by listing which integrations are currently enabled through Composio and what actions each exposes, so we both know what you can actually do.
2. When I ask for something in a connected tool ("update the deal in the CRM", "add this to the project board"), use the matching Composio action. Never invent a tool, integration, or field that Composio doesn't report as available.
3. If a task needs an integration we haven't enabled yet, don't improvise - tell me which Composio integration to switch on, and continue after I've connected it there.
4. Auth stays with me: when an integration needs a sign-in or API key, that happens in Composio's dashboard, not in this chat - never ask me to paste credentials here.
5. Side effects need my sign-off: anything that sends, posts, deletes, or changes data in a connected tool - show me exactly what you're about to do and wait for my OK. Reading and searching are fine without asking.
Confirm the setup by listing the enabled integrations now.How it is set up
Grok Bot rides on Cursor's connector catalog, which is thinner than Claude's or ChatGPT's - and sooner or later you hit a tool your bot simply can't reach natively. Corey Ganim's workaround (his second entry here, after his [Chief of Staff build](/use-cases/exact-chief-of-staff-prompt/)) is to stop collecting connectors and install a hub instead:
1. Connect the [Composio connector](/plugins/composio/) to your Grok Bot (an MCP connector like any other).
2. Connect the integrations you actually use inside Composio - it carries 1,000+ of them: CRMs, project managers, marketing tools, the niche SaaS nothing ships a native connector for.
3. Your bot now drives all of them via Composio MCP - one connector on the Grok Bot side, an entire catalog behind it.
Unsponsored, in his words: just the easiest way he's found to access tools that don't have a native Cursor connector.
Why it works
Connector catalogs are a land war - every platform grinds out integrations one at a time, and your bot's reach is capped by whichever list it sits on. A hub flips the economics: one MCP connection, and the catalog problem becomes someone else's full-time job. What makes this worth writing down rather than obvious is where the control ends up - integrations get enabled and authenticated in Composio's dashboard, not in chat, so the bot's reach is exactly what you switched on and nothing more. It's the same trick that made browser extensions and Zapier durable: don't wait for the platform to support your tool, install the layer that supports everything. And when a native connector does eventually ship, you lose nothing - the hub just quietly covered the gap in the meantime.
Before you run it
Corey's three steps, near-verbatim: connect the Composio connector to Grok Bot, connect the integrations you need inside Composio (composio.dev), and the bot uses them via Composio MCP. The prompt below is a curator reconstruction that adds sensible guardrails for a bot suddenly holding many tools.
Source
@coreyganim shared this. Read the original post.
Cursor has much fewer connectors than Claude/ChatGPT but the way to get around that is by using Composio. Your bot can now use those tools via Composio MCP. Not sponsored - just…