Source: https://qbash.com/docs/clients/grok-bot # How to add a custom MCP server to Grok Bot To add a custom MCP server to Grok Bot, ask the Bot in a chat to add the server's URL, confirm it, and sign in when the Bot posts an authorize card. :::note[Here from Google? Hi, we make the server in the screenshots] - qbash runs Tasks, which are Python programs with AI steps, alongside your connected accounts and shared memory folders. Your Bots can call all of it as tools. - You don't need qbash to follow this guide. Any remote MCP server goes in the same chat request. [What the qbash server does](https://qbash.com/docs-markdown/mcp-servers/official-mcp-server.md) ::: ## Add it in a chat 1. Open a chat with your Bot. 2. Ask it: "Add this MCP server: https://mcp.qbash.com/mcp". 3. The Bot shows the server's name and URL and asks you to confirm. Confirm it. 4. The Bot posts a card asking you to authorize qbash. Choose it, and the qbash sign-in opens in your browser. 5. Sign in and pick the qbash organization the Bot should use. Ask the Bot to list its qbash tools to check the connection. [Build a Grok Bot MCP server with qbash](https://qbash.com/blog/grok-bot-mcp-server-with-qbash) shows the whole flow on video with a custom server. The connection belongs to your Grok Bot account, so every Bot you run can use it. A teammate's shared Bot asks before it uses your qbash connection, and each teammate signs in with their own qbash account. ## On a team Any plan that includes Grok Bot lets you add a server, and it is saved to your own account. On a team, the admin's connector policy applies to Bots too: - **Teams:** Grok Bot is on by default. Admins choose allowed MCP servers in the Team Marketplace, on the dashboard's **Plugins & MCPs** page. A blocked server shows **Disabled by team admin**. - **Enterprise:** an admin turns Grok Bot on and grants your group access. If the team uses an MCP allowlist, `https://mcp.qbash.com/mcp` must be on it. If a network policy has **Apply to MCP servers** on, qbash's host must be an allowed destination. Sources: xAI's [Grok Bot teams guide](https://docs.x.ai/grok-bot/teams-and-enterprises) and [computer and apps guide](https://docs.x.ai/grok-bot/computer-and-apps), and Cursor's [model and integration management](https://cursor.com/docs/enterprise/model-and-integration-management), checked 2026-11-04. ## Grok on grok.com Grok chat on grok.com adds MCP servers separately from Grok Bot. Open [grok.com/connectors](https://grok.com/connectors), choose **New Connector**, then **Custom**, and enter the qbash URL. xAI's [connectors guide](https://docs.x.ai/grok/connectors) has the details. On Grok Business and Enterprise, members can only connect connectors an admin has added. Someone with Team Read-Write permission adds qbash in the xAI console under **Grok Business**, **Connectors**, **+ Add Connector**, **Other**. Whether the free plan can add a custom connector is unclear: xAI says connectors are for all Grok users, and third-party guides say custom servers need a paid plan. See xAI's [connector management](https://docs.x.ai/grok/connector-management).