Grok Bot is xAI's agent with its own cloud computer: you hand it a task in Slack or its app and it works on it. It already has built-in apps for services such as Gmail, Notion and Slack. For anything else with an MCP server, you add a custom connector.
As of 19 November 2026, xAI's guide says Grok Bot runs in Cursor's cloud and supports the same MCP servers, plugins and skills as Cursor.
Add a custom connector
From xAI's docs, as of 19 November 2026:
- Open the Grok Bot desktop app and go to Connect apps in the sidebar.
- Choose Add a custom connector at the bottom.
- Enter a Name and pick a Type: Remote HTTPS or Command.
- Fill in the fields for that type (below), then choose Add plugin.
Type: Remote HTTPS
- Server URL (required): the server's https address.
- HTTP headers (optional): for an API key or token.
- Client ID (optional): an OAuth client ID. A Client Secret field appears once you fill it in.
Type: Command
- Command and Arguments: what starts the server.
- It runs on the Bot's cloud computer, not on your own computer.
- A server started this way is available to your other Bots too.
That second column surprises people who come from Claude Desktop or Cursor, where a command runs on your laptop. See remote vs local MCP servers.
For example, the values for Context7, a hosted documentation server:
Context7 in Grok Bot. Add to Grok Bot desktop app → Connect apps → Add a custom connector:
https://mcp.context7.com/mcpEnter a Name (for example "Context7"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.
Built from the server's registry entry, the same config as on its listing page.
xAI's docs don't say which MCP transport Remote HTTPS uses and don't document a config file, so the form is all there is.
Servers to try
Hosted servers that answered our most recent check. We haven't tested them inside Grok Bot itself:
Hosted MCP servers for developer tools that answered our latest check, most popular first. Copy a server URL to add it.
More for developer tools
GitHub
Official MCP server connecting AI assistants to GitHub repos, issues and workflows
https://api.githubcopilot.com/mcp/Answered our last check on 19 November 2026

Context7
Version-specific library docs and code examples piped into coding agents via MCP
https://mcp.context7.com/mcpAnswered our last check on 19 November 2026

Solana MCP by Vybe
Remote MCP server exposing the Vybe Solana API to AI clients and code editors
https://mcp.vybenetwork.xyzAnswered our last check on 19 November 2026

SSRS2
Check, edit and preview RDLC reports, and turn Markdown into Word, PowerPoint or PDF
https://ssrs2.net/mcpAnswered our last check on 19 November 2026
Good to know
- Calls to a Remote HTTPS server go out from Cursor's servers.
- A Bot can add a server for you in chat, by URL or by command. If the server is on a private network or uses a private certificate authority, it asks you first.
- OAuth tokens stay on Cursor's connector backend; the Bot calls tools without seeing them.
- If your team admin's MCP policy blocks a server, you can't save it. Enterprise plans have an MCP allowlist.
- Removing an app also removes what it added, and signs you out.
In short
- Connect apps → Add a custom connector → name, type, fields → Add plugin.
- Remote HTTPS needs a URL; Command runs on the Bot's cloud computer.
- No config file to edit: the form is the whole setup.
What to try next
Share this lesson- You've now seen all six apps. Go back to the path overview for any you skipped, or move on to building: your first MCP server.