Grokbot
Add SealGate to Grokbot, xAI's cloud agent, as a custom MCP connector.
Grokbot (xAI's persistent, cloud-hosted agent - not to be confused with the Grok chat or the Grok Build CLI) runs on a remote cloud computer that can drive a browser, a terminal, and files, and reach your accounts through built-in connectors and MCP servers. It connects to SealGate as a custom MCP connector: because the bot keeps working while your laptop is closed, you add SealGate to it once, by hand, using SealGate's public gateway URL.
Grokbot reaches your MCP server from xAI's cloud, not from your machine. Your connection URL must therefore point at SealGate's public gateway (https://mcp.sealgate.ai/...) - a localhost URL from the desktop app's local injection will not work for Grokbot, which cannot reach a server that only exists on your laptop.
Grokbot is an xAI beta on its paid tiers. Confirm availability on your plan before rolling SealGate out.
1. Get Your SealGate Connection URL
Your personal connection URL embeds your API key. For Grokbot, append ?client=grokbot so SealGate tags the session as Grokbot in the dashboard:
https://mcp.sealgate.ai/mcp/<your-api-key>/?client=grokbotThe easiest way to get this URL is from the SealGate dashboard: open Settings, find the Api key / MCP URL section, click Get MCP URL, and pick Grokbot from the list - the dialog gives you a ready-to-copy URL with the ?client=grokbot tag already appended. (Alternatively, copy the base URL from the SealGate desktop app's Copy MCP URL menu and add ?client=grokbot yourself.) Treat this URL like a password - anyone with it can call MCP tools as you (subject to your Access Control Levels and policies).
The ?client=grokbot tag matters beyond the display label - SealGate relies on it to recognize Grokbot and group its calls into the right session, so always include it.
The host differs per environment - release is mcp.sealgate.ai, and demo/self-hosted deployments use their own gateway host. Always copy the URL from your own desktop app rather than hardcoding the host.
2. Add SealGate as a Custom MCP Connector
Connectors are configured on your own Grokbot account, so each user's SealGate traffic is attributed to them - simply have every member add their own connection URL.
- Open Grokbot's Connectors / MCP settings and choose to add a custom MCP server.
- Under Transport, choose Streamable HTTP - SealGate's gateway speaks streamable HTTP.
- Paste your full connection URL from step 1 as the Server URL, including the trailing slash and
?client=grokbot. - Set Authentication to None. SealGate authenticates via the API key in the URL - it has no OAuth sign-in and needs no separate header.
- Save the connector. Grokbot will connect and discover SealGate's tools, then use them on its cloud computer.
Because every SealGate connection URL embeds a personal, per-user API key, do not share one connector's URL across a team. Distribute the SealGate desktop app so each member can copy their own connection URL and add it to their own Grokbot account - that keeps every member's traffic correctly attributed to them in the SealGate dashboard, where admins get org-wide visibility across all of them.