How to connect MCP servers to Grok Bot

You can ask Grok Bot to add an MCP server in a chat, but there’s a better way: use an MCP gateway.

A gateway gives you one MCP connection with all of your MCP servers behind it. MCP1 is an MCP gateway by Appwrite. Connect Grok Bot to it once, manage your servers from one dashboard, and share the same set with your coding agents. This guide shows you how.

Why a gateway is better for more than one server#

Adding servers one at a time has three costs:

• You set up every server again in each client. Adding Linear to Grok Bot does nothing for Claude Code or Cursor.
• You sign in to every server, or paste its token, in every client.
• Nothing shows you which servers each client has, or which tools those clients called.

With MCP1, Grok Bot connects once and you manage the rest in a dashboard:

• Add servers without setting up Grok Bot again. Pick from a catalog of 154 servers or add any remote MCP server by its URL. The free plan includes 15 servers, and paid plans go up to 1,000.
• Manage everything in one place. Turn tools on or off, choose who can call them, and read a record of every call.
• Use the same servers everywhere. Grok Bot, Claude Code, Cursor, ChatGPT, Codex and any other client that speaks remote MCP connect to the same URL.
• Keep tokens out of your clients. MCP1 seals each server’s credentials, and Grok Bot never sees them.

Add your MCP servers to MCP1#

You need an MCP1 account with a verified email address. You can’t approve a client until you verify it.

1. 1Create a workspace, or open one you already have.
2. 2Open Catalog and install the servers you use. If a server isn’t listed, select Add by URL.
3. 3Open Gateways, pick a gateway and select Add servers.

Copy your gateway URL#

Every gateway has its own URL, and Grok Bot can’t guess yours. To find it:

1. 1In your workspace, open Connect a client.
2. 2Under Gateway, pick the gateway you want Grok Bot to use.
3. 3Under Your app, choose Any MCP client.
4. 4Copy the URL.

https://mcp1.com/mcp/<workspace>/<gateway>

The URL of a workspace’s default gateway ends at the workspace: https://mcp1.com/mcp/<workspace>.

Connect the gateway to Grok Bot#

MCP1 isn’t in Grok Bot’s connector catalog, but Grok Bot can add it by its URL. Open a chat with your bot, then follow these steps:

1. 1Ask Grok Bot to set up the MCP1 server. It tells you that MCP1 isn’t in the catalog and asks for your gateway URL.
2. 2Paste the URL into the chat. Grok Bot adds the gateway and shows a card with a Connect button.
3. 3Select Connect.
4. 4Sign in with your MCP1 account and approve Grok Bot.

After you approve it, Grok Bot calls MCP1 as you, with your own access. Its tokens last eight hours and refresh on their own, so you sign in once.

Check which tools Grok Bot can use#

Ask Grok Bot which MCP1 tools it has. MCP1 treats Grok Bot the same as any other client:

• Tools are named server__tool, and Grok Bot sees only the ones your access allows. A read-only grant hides the tools that write.
• Ask first rules ask you in the client before the call runs. If a client can’t show the question, MCP1 refuses the call. Grok Bot also asks before it makes changes, separately from MCP1.
• The audit log records every call, with who made it and from which client.
• Missing tools have an explanation. Ask Grok Bot to call mcp1__check_access, which says why a tool is or isn’t open to you.

Share the same servers with your coding agents#

Connect your other clients to the same URL. In Claude Code, that’s one command:

claude mcp add --transport http mcp1 https://mcp1.com/mcp/<workspace>/<gateway>

Then run /mcp, pick mcp1 and choose Authenticate.

The same URL works in Cursor, VS Code, ChatGPT, Codex, Windsurf and Gemini. The docs have the steps for each client.

Other assistants work the same way. An assistant that can add a remote MCP server by its URL can use a gateway. If it doesn’t support OAuth, it can send an API key instead.

A gateway can also hold your own tools. With a T3 Code MCP server behind it, for example, everything connected to the gateway could interact with T3 Code. MCP1 connects only to remote servers, so that server has to be reachable at a public URL.

Disconnect Grok Bot#

You can disconnect from Grok Bot at any time. To cut access from MCP1, open Clients in your workspace and select Revoke client. Every token issued to Grok Bot stops working, and you have to approve it again before it can reconnect.

What’s next#

Create a workspace if you don’t have one, then add your first servers from the catalog. To bring a whole team on, read 10 steps for rolling out MCP across your company.