Grok Bot Plugins: Install, Connect And Stack 200 Skills (2026)

Grok Bot plugins are the packaged app connectors you install from Connect apps so a Bot can work inside Gmail, Notion, Slack or Linear through tools instead of clicking around a website.

Since v0.71.2 on 14 October 2026, the per-Bot ceiling on plugin skills jumped from 24 to 200.

That change is the reason I'd rebuild my plugin setup now rather than later.

Below is the exact order I'd do it in: install, sign in, attach, add custom servers, then lock down approvals.

If you want a second pair of eyes on which apps to wire up first, book a free SEO strategy session with my team and we'll map it with you.

What a Grok Bot plugin actually gives your Bot

A plugin hands the Bot a structured set of tools for one service.

The official computer and apps docs say apps are more reliable than clicking through a website when one exists.

Use the Bot's browser only for services with no app, or for visual flows an app doesn't expose.

Three rules shape every setup decision after this.

Apps are account-wide. Connect one and every Bot you run can use it.
Tokens stay off the computer. OAuth tokens sit on Cursor's connector backend, and the Bot calls tools without receiving them.
No extra access. A plugin can do only what the authorized account can already do, and it can't change sharing.

So the account you sign in with is the real permission boundary.

Pick it on purpose.

Step 1: Install a plugin from Connect apps

In the sidebar, click Connect apps. Phone users get there through the avatar in the top-left corner.
Browse or search for the app. Since v0.70.2 the list shows the most-installed plugins first.
Choose Add. Since v0.77.0, Add installs the plugin and opens sign-in in one click.
Complete the provider's own login page when Grok Bot asks you to Authorize or Authenticate.
Confirm the app now sits under Installed.

If sign-in stalls, choose Reconnect on the app, or Reopen on the in-chat card.

Both version notes come from the Grok Bot changelog.

Step 2: Or tell the Bot to install it for you

The faster route is one line in chat.

Type “Add the Linear app.”

It looks the app up in the catalog, installs it for your account, and drops a Connect card into chat for the sign-in.

Paste a connector link instead and, since v0.70.2, the Bot installs the matching plugin from the catalog.

Ask for an app that isn't installed and, since v0.77.0, the Bot checks the plugin catalog and links it in Connect Apps.

Since v0.75.8, a plugin the Bot installs mid-task has its skills usable right away.

🔥 Want the plugin playbook as step-by-step video? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members wiring agents into their own apps. → Join the AI Profit Boardroom

Step 3: Check the sign-in, not just the install

This is the trap that wastes the most time.

Added means the plugin is installed, not that you are signed in.

When the Bot reports a missing app, go back to that app's card in Connect apps.

Look for Needs auth or Disconnected.

Choose Authenticate on desktop, or Authorize on the phone.

For routines, v0.75.2 added a Reconnect card in chat, shown at most once a day, when a routine hits a signed-out connector.

I'd treat that card as a to-do, not noise.

Step 4: Attach the plugin to a task with @

In any chat, type @ and pick the app to attach it to the task.

The same @ menu covers Bots, groups and routines, according to the skills and routines docs.

Attaching makes your intent explicit, so the Bot doesn't guess between the browser and the plugin.

I'd attach on every first run of a new workflow.

The 200-skill ceiling and how I'd spend it

Plugins ship packaged skills, and skills are reusable instructions for a job.

At 24 skills, a Bot carrying three or four business plugins ran out of room fast.

At 200, one Bot can carry a full stack: inbox, calendar, docs, tickets and chat.

More room is not a reason to install everything.

Every extra skill is one more path the Bot can choose.

Here's how I'd split it:

One operations Bot with the plugins it touches daily.
Private skills written for your exact process, saved after a clean one-off run.
Plugins you only need monthly left uninstalled until that job comes round.

Private skills live in one library shared by all your Bots.

If a Bot can't see one, open Connect apps, select the connected count next to the title, and enable it under Private skills for that Bot.

Add an MCP server that isn't in the catalog

The catalog isn't the ceiling.

Hand the Bot a server URL, or a launch command for its cloud computer, and it wires the MCP server in.

Command-launched servers are then shared with every other Bot on your account.

Adding a server on a private network, or one that uses a private certificate authority, asks for your approval first.

On a team with an allowlist network policy, there's a catch in the Grok Bot security docs.

Bots reach remote MCP servers from Cursor's servers, so the allowlist doesn't cover them on its own.

An admin has to turn on Apply to MCP servers to hold them to the same list.

Per-app gotchas to check before the first task

The docs list hard limits per app. I'd read these before I promise anyone a workflow.

Plugin	What it does	Gotcha
Google Calendar	Reads calendars, creates and updates events, checks free time	Can't change Meet settings or add a Zoom link
Google Sheets	Reads and edits cells the account can edit	Viewer files stay view-only; finding files uses the Google Drive app
Slack	Posts as the Slack user you connected	Only in channels that user can post in; one workspace per connection
Gmail	Searches, reads, drafts, sends, labels	One mailbox at a time
X	DMs, bookmarks, home timeline	Needs X API credits on your X developer account

Notion is the opposite of Gmail here: the docs say it can connect a second account.

Public X search needs no plugin at all, because Bots can read public X without signing in as you.

Connecting X also connects X Money, per v0.75.5.

Google says an admin needs to review Grok: the fix

Company Google accounts can stop the sign-in for Gmail, Calendar, Drive, Docs, Sheets or Slides.

The page reads Your admin needs to review Grok.

Grok Bot signs in to Google as Grok, not Cursor, so your IT admin has to trust that app.

Open Security, then Access and data control, then API controls.
Open App access control, then Manage third-party app access.
Add the app named Grok, or search by the client ID from the blocked page.
Set Grok to Trusted for the people who use Grok Bot.

Switching browsers won't clear a Google admin block.

Only the admin change does.

📞 Mapping plugins to a real business process? Book a free SEO strategy session and my team will walk through which connectors and skills save you the most hours. → Get your free strategy session

Wire 1Password in as the login plugin

For sites with no app, the Bot signs in through the browser.

Vault is checked first, a password manager such as 1Password second, and a Secure Form request to you comes last.

1Password sits under Password Managers in Connect apps and needs 1Password 8.12.42 or later.

You approve each login in 1Password, and it fills the Bot's browser without the Bot seeing the values.

Two limits matter: it only offers logins from your Personal vault (Private on Family accounts), and it doesn't fill payment cards.

If you used the old service-account integration, connect it again.

Team setups: connector policy and shared Bots

On a team, Grok Bot inherits the Cursor connector policy, and there's no separate Grok Bot list.

Admins set allowed servers in the Team Marketplace on the Plugins & MCPs page, per the teams and enterprises docs.

A blocked plugin shows Disabled by team admin, a label the changelog added in v0.77.0.

Admins can't push connectors to members, so mandatory or default-on installs aren't available.

The MCP allowlist is Enterprise only.

Blocking a plugin doesn't block that service's website; closing that path takes Network Controls, also Enterprise only.

Shared Bots keep their own Plugins, Secrets, Skills and Files in Bot settings.

A teammate's shared Bot asks before it uses your accounts.

From v0.77.0 on, each linked teammate brings their own connectors and memory to a Team Bot.

Since v0.78.1, a Team Bot routine that needs one of your connectors asks in the routine's Slack thread and tags you.

Remove or repair a plugin without losing a day

Removing an app deletes everything it added and signs you out.

Reinstalling means signing in again, so don't remove a plugin just to “reset” it.

Apps your team requires can't be removed at all.

Two known issues are in the docs right now.

Zoom authorization from the desktop app fails with error 4700, with no workaround yet.

SharePoint connected with Application-level permissions shows AADSTS50011; connect with Delegated permissions instead.

My checklist for every new plugin

Install it from Connect apps, or say “Add the <app> app” in chat.
Confirm it shows under Installed and isn't marked Needs auth.
Run one task with the plugin attached via @.
Save the clean run as a private skill with an approval rule written in.
Add an Ask first rule for sending, posting, deleting and buying.
Only then build a routine on top of it.

Grok Bot is included on the Premium, Super and Ultra plans, and Plus doesn't include it, per the X Subscription docs.

If you'd rather get the whole agent stack handed to you, the AI Profit Boardroom has the trainings and the installable Agent OS ready to go.

Want the plugins mapped to your own business? Grab a free strategy session and start with the three apps you open most.

Also On Our Network

FAQ: Grok Bot Plugins

Why does my Grok Bot say an app is missing after I added it?

Added only means installed. Open the app in Connect apps and choose Authenticate (Authorize on the phone) if it shows Needs auth or Disconnected.

Can a Grok Bot install a plugin by itself?

Yes. Ask it to add the app and it searches the catalog, installs it and shows a Connect card for sign-in. Since v0.75.8 its skills are usable right away.

How do I connect an MCP server that isn't in the catalog?

Ask the Bot to add it by URL or by a command on its computer. Servers on a private network or with a private certificate authority ask for your approval first.

Why can't the Bot add a Zoom link to my calendar events?

The Google Calendar app can't use Google's Zoom add-on. Put the Zoom link in the event location or description yourself.

Does 1Password fill payment cards for the Bot?

No. 1Password fills logins from your Personal or Private vault only, and payment cards come from Vault, a Secure Form or a connected wallet.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Install one app tonight, sign it in, attach it with @, and book a free strategy session if you want help choosing the next ones for your grok bot plugins.