Grok Bot custom MCP lets you plug your own Model Context Protocol server into every Bot on your account, either as a Remote HTTPS endpoint or as a Command that starts on the Bot's cloud computer.
Here's how I'd set it up: pick the type, fill in the form, authenticate, test it with a read-only task, then check the two policy layers that can still block it.
Every field name and rule below comes from the official computer and apps docs, the Grok Bot security page and the teams and enterprises guide, all read on 12 November 2026.
If you want my team to map which of your tools deserve a connector, book a free SEO strategy session and we'll plan it with you.
Pick the server type before you open the form
The custom connector form has exactly two types, and the choice changes how policy treats the server later.
Remote HTTPS is a server that lives somewhere else and answers at a URL.
Command is a server that the Bot's computer starts by running a program with arguments.
Pick Remote HTTPS when a vendor hands you a hosted endpoint.
Pick Command when you have a server package or a script you run yourself.
| Field | Remote HTTPS | Command |
|---|---|---|
| Name | Required | Required |
| Main field | Server URL | Command |
| Extra fields | Optional HTTP headers, optional OAuth Client ID (a Client Secret field appears once you enter one) | Arguments |
| Where Bots reach it | From Cursor's servers | On the Bot's computer |
| Network allowlist coverage | Only when Apply to MCP servers is on | Already covered by the network policy |
That last row trips up most admins, so keep it in mind until the Enterprise section below.
Step 1: Check the catalog, then open Add a custom connector
Search the catalog first.
The Grok Bot changelog (v0.70.2, 11 October 2026) says that when you give a Bot a connector link, it installs the matching plugin from the catalog, and Connect Apps lists the most-installed plugins first.
If the service is already there, use the catalog app and skip the custom form.
For catalog apps, reconnect cards and timeouts, my Grok Bot connectors walkthrough covers the details.
If it isn't there, open Connect apps from the sidebar of the desktop app.
Scroll to the bottom and choose Add a custom connector.
The docs describe this manual form in the desktop app, so do it from your Mac or Windows machine.
Step 2: Fill in a Remote HTTPS server
Type a Name you'll recognize when you attach it in chat.
Set Type to Remote HTTPS.
Paste the vendor's Server URL.
Add HTTP headers only if the vendor's own docs ask for them.
If the server signs in with OAuth, enter the OAuth Client ID; the Client Secret field appears once you do.
Choose Add plugin to save.
Here's the shape of the form for a job-tracking tool (the hostname is a placeholder, swap in your vendor's real endpoint):
Name: Job Tracker
Type: Remote HTTPS
Server URL: https://mcp.example.com/
HTTP headers: (only if the vendor's docs require one)
OAuth Client ID: (from the vendor's developer settings)
Client Secret: (field appears after the Client ID)
-> Add pluginA quick sanity check before you press save: open the vendor's MCP page and confirm the URL starts with https.
If the vendor offers OAuth, use it rather than a static header, because the docs confirm OAuth tokens are held on Cursor's connector backend and never handed to the Bot.
The docs don't make that same promise about header values.
If the vendor only offers a header, set it up the way their docs describe and keep that server off any Bot that doesn't need it.
Step 3: Fill in a Command server
Set Type to Command.
Put the program in Command and everything after it in Arguments.
Choose Add plugin.
Name: Stock Sheet
Type: Command
Command: python3
Arguments: /workspace/mcp/stock_server.pyKeep the script inside /workspace, the shared workspace the files section of the docs tells you to use for durable project files.
Here's the gotcha: the docs treat manually installed packages as replaceable.
Project folders such as node_modules or a Python virtual environment are not saved, so reinstall them after a computer update, Recover or Reset.
If your command server suddenly stops answering after a Recover, check its dependencies first.
Step 4: Authenticate, then confirm it under Installed
Added only means installed.
It does not mean you're signed in.
If the server shows Needs auth or Disconnected, open it and choose Authenticate (Authorize on the phone).
If the provider login doesn't finish, choose Reconnect to bring the sign-in page back.
Then confirm the server appears under Installed.
🔥 Want the exact connector setups other operators are running? Inside the AI Profit Boardroom you get step-by-step video trainings on wiring Bots to real tools, the installable Agent OS, four coaching calls a week and 3,400+ members comparing setups. → Join the AI Profit Boardroom
Step 5: Attach it with @ and run a read-only first task
In chat, type @ and pick your server to attach it to the task.
The recommended configuration tells members to start new roles with read-only tasks and draft outputs.
So make the first job something that only reads:
@Job Tracker list every job marked open, with the customer name and
the date it was booked. Don't change anything. Show me the result as a table.If the answer comes back clean, move on to a draft-only task next.
Keep sending, publishing, deleting and anything that touches money behind approval, as the same guide says.
The shortcut: ask the Bot to add the server for you
You don't have to fill in the form yourself.
A Bot can add an MCP server that isn't in the catalog, by URL or by a command that runs on its computer.
Two details matter here.
A server started by a command becomes available to your other Bots too.
And if the server sits on a private network or relies on a private certificate authority, you get an approval card before it's added.
Add this MCP server as a custom connector: https://mcp.example.com/
Call it Job Tracker. Tell me if it needs me to sign in, and don't
run any of its tools until I say so.Read the approval card before you press anything.
If the server is on a private network, that card is your one chance to stop it.
Gotcha: every Bot shares one computer and one app list
The shared computer section is blunt about this.
Every Bot on your account uses the same computer.
Files are visible to every Bot, browser sessions are shared, and command-line credentials are shared too.
Each Bot gets its own screen, yet the docs call those screens work surfaces rather than security boundaries.
Apps are account-wide as well, so a connected server is available to every Bot you run.
If one Bot shouldn't touch a server or a credential, don't put it on that account.
Between users it's different: each user's computer is dedicated and hardware-isolated, so your teammates' Bots never land on your machine.
A teammate's shared Bot also asks before it uses your accounts.
Where tokens and secrets actually live
OAuth logins stay off the computer.
The tokens sit on Cursor's connector backend, and the Bot calls the server's tools without ever receiving them.
For an API key, enter it in the masked secure secret card when the Bot asks; the Vault docs on secrets confirm the value stays out of the chat log and hidden from the Bot.
Never paste a password, key or one-time code into ordinary chat.
And only add servers you trust, because a server acts as the account you sign it into, with exactly that account's reach.
When the form refuses to save: the team MCP policy
If your team admin's MCP policy blocks a server, the form can't save it.
Grok Bot inherits the team's Cursor connector policy, and there's no separate Grok Bot connector list.
Admins set permitted servers on the dashboard's Plugins & MCPs page, not on the Grok Bot page.
A blocked server shows Disabled by team admin.
The fix, per the admin FAQ, is three moves:
- The admin enables the server in Teams Marketplace.
- The admin adds its server URL to the MCP allowlist, if the team uses one.
- You restart the app.
If a permitted server still fails with a permission error from the vendor, check the vendor's requirements.
Some vendors restrict their MCP endpoints to their own administrators.
Enterprise: the allowlist and the Apply to MCP servers switch
The MCP allowlist is Enterprise only, and so is Network Controls; Cursor's MCP server trust management page covers the allowlist side.
Here's the part people miss.
Bots reach remote MCP servers from Cursor's servers, so an allowlist network mode does not cover them on its own.
To hold remote servers to the same list, turn on Apply to MCP servers.
It's off by default for every team, and it only shows while Default, plus the allowlist or Allowlist only is selected.
When it's on, a remote server must match an entry in Allowed destinations, or it's refused when a Bot tries to use it.
Command servers are unaffected, because the network policy already applies to them.
Expect roughly a minute before a change lands, and it takes effect from the next MCP connection.
This is the refusal your members will see:
MCP server "<host>" refused: it is not on your team's Grok Bot network allowlist (Grok Bot settings > Network > Allowed destinations). A team admin can add it.Built-in connectors are checked by the hosts they call too, so add hosts such as api.github.com and api.x.com before you flip the switch.
Team Bots: custom servers are shared with everyone
The 11 November 2026 release (v1.0.1) on the changelog changed one thing for Team Bots.
From that release, any custom MCP connector you add to a Team Bot is listed as shared with the whole team, and the Share my account choice isn't offered for it.
So treat any custom server you attach to a Team Bot as team-wide from day one.
Use a service account sized to the job rather than your own login.
📞 Not sure which of your tools should become a connector? Book a free SEO strategy session and my team will look at your stack, your site and where Bots fit. → Book my free strategy session
Removing a server without surprises
When a Bot removes an app for you, everything the app added goes with it and you're signed out.
Reinstalling it means signing in again.
Apps your team requires can't be removed at all.
Review connected apps and active routines regularly, and pause a routine when its source system changes.
My pre-flight checklist before any custom server goes live
- Search the catalog first; use the catalog app if it exists.
- Pick Remote HTTPS for a hosted endpoint, Command for a script you run.
- Keep command scripts in
/workspaceand note their dependencies. - Authenticate and confirm the server sits under Installed.
- Run one read-only task with
@before anything that writes. - Check the team policy, and on Enterprise, the Apply to MCP servers switch.
- Prefer Allow once over Always allow for actions that touch accounts, money or shared resources.
Want the full Agent OS build around this, plus coaching while you set it up? Join the AI Profit Boardroom and bring your server to the next call.
Also On Our Network
- 🌐 When a small business should add its own MCP server, with five examples
- 🌐 An eight-row scorecard rating custom MCP servers on safety and control
- 🌐 Five copy-paste prompts that make your Bot add and check its own servers
- 🌐 Which models to pair with a custom server, using live GoldieBench scores
FAQ: Grok Bot Custom MCP
Where is the Add a custom connector button in Grok Bot?
At the bottom of Connect apps in the desktop app. Enter a Name, pick Remote HTTPS or Command, fill the fields and choose Add plugin.
Why does my custom server say Added but the Bot can't use it?
Added means installed, not signed in. Open it and choose Authenticate (Authorize on the phone) if it shows Needs auth or Disconnected.
Does a Command server need the Apply to MCP servers switch?
No. Command servers run on the Bot's computer, and the network policy already applies to them. The switch is for remote servers.
What happens if I add a server on a private network?
When a Bot adds a server on a private network, or one using a private certificate authority, it asks for your approval first.
Why won't the custom connector form save?
Your team admin's MCP policy blocks that server. The admin enables it in Teams Marketplace and, if the team uses one, adds it to the MCP allowlist.
📺 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
Add one trusted server today, test it read-only with @, and book a free strategy session if you want my team to plan the rest of your grok bot custom mcp setup.











