Grok Bot Connectors and Custom MCP Servers: Setup Guide
Last updated
Last verified against official xAI documentation on November 16, 2026.
A Grok Bot is only as useful as the apps it can reach. Connectors give it a direct line into tools like Gmail, Slack and Notion. A custom MCP server does the same for a tool that is not in the catalog, including software you built yourself. This guide covers both: how to connect a catalog app, how to add your own MCP server, who on your team can use it, and what to check when sign-in fails.
Connectors, plugins and MCP in one minute
Three words get used for nearly the same thing, so here is how they fit together.
- MCP (Model Context Protocol) is an open standard that lets an AI assistant call tools in other software. An MCP server is the piece that offers those tools.
- An app or plugin is an entry in the Grok Bot catalog. You find it under Connect apps.
- A custom connector is an MCP server you add yourself because the catalog does not have it.
Whichever route you take, the rule on access is the same. The xAI docs say an app can only do what the account you authorized can already do in that service. It cannot raise your access or change sharing (Use the computer and apps, xAI docs).
Step 1: Connect an app from the catalog
Start here. If the catalog has the app, you do not need a custom server. The desktop steps from the docs (Use the computer and apps):
- Open Connect apps from the sidebar, or follow a Connect card the Bot posts in chat.
- Browse or search for the app and add it.
- When Grok Bot asks you to Authorize or Authenticate, finish the provider login in your browser.
- Confirm the app appears under Installed.
In the mobile app, tap your avatar in the top left and choose Connect apps. On the phone the sign-in button reads Authorize.
You can also skip the menu and ask. The docs use the example "Add the Linear app." The Bot searches the catalog, installs the app on your account, and shows a Connect card if you need to sign in. The app's tools are available from your next message.
Two status labels are worth knowing. Added means the app is installed but not signed in. Needs auth or Disconnected means you should open the app and sign in again.
Step 2: Add a custom MCP server
When the catalog does not have your tool, add its MCP server as a custom connector. This is done in the desktop app. Per the docs (Use the computer and apps):
- Open Connect apps and choose Add a custom connector at the bottom.
- Enter a Name you will recognize later.
- Pick a Type: Remote HTTPS or Command.
- Fill in the fields for that type (see the table below).
- Choose Add plugin to save.
| Type | Use it when | Fields |
|---|---|---|
| Remote HTTPS | The vendor hosts the server and gives you a web address | Server URL (required), HTTP headers (optional), OAuth Client ID (optional). A Client Secret field appears once you enter a Client ID. |
| Command | The server is a program that runs on the Bot's computer | Command and Arguments |
You can also ask a Bot to do it. The docs say a Bot can add an MCP server that is not in the catalog, by URL or by a command that runs on its computer. A prompt like this works:
Add the MCP server at https://mcp.example.com/mcp as a custom connector called "Inventory." Tell me which tools it offers before you use any of them.
Two details from the docs to keep in mind. A server on a private network, or one that uses a private certificate authority, needs your approval before it is added. And if your team admin's MCP policy blocks the server, it cannot be saved at all.
Which sign-in method to use
Most hosted MCP servers use one of two methods. Check the vendor's setup page to see which.
- OAuth. You add the URL, then sign in on the vendor's site when the Connect card appears. Some vendors ask you to register a client first. If so, paste the client ID and secret they give you into the connector form.
- API key. The vendor gives you a key that goes in a header, often
Authorization: Bearerfollowed by the key. Put it in HTTP headers on the connector form. Do not paste the key into ordinary chat. The docs say passwords, one-time codes and API keys should stay out of the chat transcript (Approvals, security and privacy).
Step 3: Test it with a read-only task
Type @ in the message box to attach the app to a task (Use the computer and apps). Make the first task something that only reads:
Using @Inventory, list the five products with the lowest stock. Do not change anything.
Check that the answer matches what you see when you log in to the tool yourself. Only then move on to tasks that write, send or delete. The xAI security page gives the same advice: start with read-only tasks and draft outputs (Approvals, security and privacy).
Who can use a connected app?
Apps are account-wide. Once you connect one, every Bot you run can use it. There is no per-Bot switch. A command server that one Bot starts is available to your other Bots too (Use the computer and apps).
Team Bots work a little differently. A teammate's Team Bot asks before it uses your accounts. In the other direction, the apps, secrets, skills and files a Team Bot's owner adds work in every teammate's chat with that Bot (Approvals, security and privacy). Treat anything you connect to a shared Bot as shared with the people who use it.
Some apps can hold more than one account, for example two Notion workspaces. Open the app in Connect apps, choose Add Another Account under Accounts, enter a label, then choose Authorize. If you do not see that option, the app supports one account. Gmail connects one mailbox at a time.
Approvals: what the Bot asks before it acts
A connector decides what the Bot can reach. Approvals decide what it does without asking. Auto Review is on by default and checks each action before it runs, including use of a connected app. Most actions run without a prompt. When one needs your OK, an approval card shows the operation and its inputs with three choices: Allow once, Always allow and Deny (Approvals, security and privacy).
For anything that matters, add a rule. On desktop, go to Settings, then General, then Bot, and find Custom Rules under the Auto-review switch. Describe the action and choose Ask first. When an Ask first rule and an Allow rule both match, Ask first wins. You can keep up to 20 rules of each kind.
A good first rule for a new connector, in the style the docs suggest:
Ask first before creating, updating or deleting any record through the Inventory connector.
The docs are plain about the limits of this safety net. Auto Review is a model's judgment, and they say it should complement least privilege and clear approval boundaries, not replace them.
Team and admin controls
If you use Grok Bot through a team, your admin decides which connectors you can add. The points that matter, from the xAI teams page (Teams and enterprises):
- Connector policy applies on every plan. Grok Bot has no separate connector list. Admins set which MCP servers members can use on the dashboard's Plugins & MCPs page.
- A blocked app shows "Disabled by team admin." Ask your admin to enable it. Blocking an app does not block that service's website.
- The MCP allowlist is Enterprise only. If your team uses one, a custom server's URL has to be on it.
- Admins cannot push connectors to members. The docs list mandatory or default-on connectors as not available.
- Google BigQuery and Databricks Genie need admin setup first on the Plugins & MCPs page (Use the computer and apps).
The docs recommend that admins review the connector policy before turning Grok Bot on for a team.
When a connection fails
| What you see | What to do |
|---|---|
| Sign-in never finishes | Choose Reconnect on the app, or Reopen on the in-chat card. Finish within about 10 minutes or start again from the card. |
| Needs auth or Disconnected | Open the app and choose Authenticate (Authorize on the phone). |
| Disabled by team admin | Your team's connector policy blocks it. Ask your admin. |
| The custom connector will not save | Your team's MCP policy blocks that server. Ask your admin to allow it. |
| Google blocks the connection | A Google Workspace admin has to approve Grok. The Bot signs in to Google as Grok. |
| Microsoft 365 asks for admin approval | Outlook, Outlook Calendar, OneDrive and Teams can need it. Retrying does not help. Contact your Microsoft admin. |
| Zoom fails with error 4700 | A known issue when authorizing from the desktop app. The docs list no workaround yet. |
| The phone says Connect on your computer | A few apps can only be connected from the desktop. Once connected there, they work on the phone too. |
All rows are from the xAI docs (Use the computer and apps). Two more quirks from the same page: Stripe connections end a fixed time after sign-in, so expect to reconnect now and then, and the X plugin needs X API credits on your developer account.
How to remove a connector
The security page says to do two things: uninstall the connector in Grok Bot, and revoke its authorization in the source service (Approvals, security and privacy). The second half is easy to forget. Until you revoke it on the vendor's side, the grant can still exist there.
If you ask a Bot to remove an app, everything the app added is removed and you are signed out. Apps your team requires cannot be removed (Use the computer and apps).
Quick safety checklist
- Connect only the tools a workflow needs.
- Use a scoped service account where the vendor supports one, so the Bot gets less access than your own login.
- Only add custom MCP servers from a vendor you already trust with that data.
- Keep sending, purchasing, deleting and publishing behind an Ask first rule.
- Do not approve an action when you cannot tell what it targets.
- Review your installed connectors and active routines on a schedule.
The first, second, fourth, fifth and sixth items come straight from the xAI security page (Approvals, security and privacy). The third is our own advice.
Common questions
Does Grok Bot support MCP?
Yes. You can add an MCP server as a custom connector, either a remote HTTPS address or a command that runs on the Bot's computer (Use the computer and apps).
Can I add a custom connector from my phone?
The docs describe the custom connector form for the desktop app only. Add it there. Connected apps then follow your account.
Does the Bot see my password or token?
For apps you sign in to with OAuth, the docs say the tokens are held on Cursor's connector backend and the Bot calls tools without receiving them (Use the computer and apps).
Can I limit a connector to one Bot?
No. Connected apps are account-wide, so every Bot you run can use them. Use Custom Rules and a scoped account to narrow what happens.
Next step. Once an app is connected, put it to work on a schedule with Grok Bot routines and skills.
Need a connector that does not exist yet? CNR Consulting builds custom MCP servers and sets up Bots around the tools you already use. See fixed-price setup.
Compare plan prices with the free AI cost calculator.