// AI Advantage
One Set of Keys for All Your AI
Grok, Claude, and ChatGPT each want their own keys to your apps. This week: the one dashboard that manages access for all your AI — and the audit prompt to paste before you hand any of them real work.
Yesterday I told you to hand Grok Bot its first real job with the fewest permissions that let it finish. Here's the problem that shows up about a week later: you don't have one AI anymore. Neither do I. I've got Grok watching competitors, Claude running my content pipeline, ChatGPT doing odd jobs — and every one of them wants its own OAuth handshake into Gmail, Slack, Notion, and GitHub. Three chatbots times a dozen apps, and pretty soon you can't answer the most basic security question in the building: what can my AI actually touch? The fix I use is Composio Connect, Composio's universal MCP server — one endpoint every chatbot points at, one dashboard where you grant and revoke everything. You stop handing out keys and forgetting who has them. You become the person holding the keyring.
My Composio dashboard. That's 6,910 tool calls my AIs have made against apps I authenticated once — and one page where I can see, and cut off, every connection.
The setup is one URL
Sign in at composio.dev, then point each chatbot at the same endpoint: https://connect.composio.dev/mcp. In Grok, that's grok.com/connectors → New Connector → Custom — Grok takes any MCP server reachable over the public internet. Claude, ChatGPT, and Cursor connect the same way through their connector and developer settings. Then you authenticate each app — Gmail, Slack, Notion, your CRM — exactly once, and every chatbot on the endpoint can use those connections at whatever access level you granted.
Then paste this into each chatbot before you hand it real work — it's yesterday's audit discipline, automated:
You're connected to my tools through Composio. Before we do any work together:
1. List every app you can reach through Composio on my account, with the
access level each connection grants (read, write, send, delete).
2. Flag any connection with write, send, or delete access to
[EMAIL / CALENDAR / CRM / FILES].
3. I've hired you for one job: [DESCRIBE THE ONE JOB]. Tell me which
connections that job actually needs — and which I could revoke
without breaking anything.
Output a table: App | Access | Needed for this job? | Recommendation.
Sample output (Grok, on the competitor-digest job from yesterday's Lesson):
App | Access | Needed for this job? | Recommendation
Gmail | Read + send | Yes | Keep — delivers the digest
Slack | Read + write | No | Revoke until a job needs it
Notion | Read + write | No | Revoke until a job needs it
GitHub | Read | No | Revoke — unused by this job
What changes: You stop maintaining a separate permission trail per chatbot, and start running AI access like an IT department of one — every grant visible, every revoke instant, all in one place.
Where else this works: The same audit prompt covers onboarding any new agent, a quarterly access review, offboarding a chatbot you stopped using, or checking what a departing employee's AI could still reach.
Why this week? Grok Bot just dropped to $20 a month, and if you followed yesterday's Lesson, it starts its first job Friday. Composio Connect covers more than 1,000 apps with OAuth handled for you, and Composio's free tier — 100,000 tool calls a month, no credit card — is more than a personal stack burns. Ten minutes tonight puts every key your AI holds on one ring. Do it before the agents multiply. They will.
Grok week wraps tomorrow in the AI Deep Dive: did xAI just prove the leaderboard is the wrong way to buy AI?
