Grok
Add SealGate to Grok as a custom MCP connector via grok.com Connectors.
Grok (xAI's chat at grok.com) connects to SealGate as a custom MCP connector. Grok discovers the tools your MCP server exposes and makes them available in conversations, alongside its built-in and catalog connectors. Like claude.ai and ChatGPT, Grok runs in xAI's cloud, not on your laptop - so you add SealGate to it once, by hand, using SealGate's public gateway URL.
When you add a custom connector, Grok 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 Grok, which rejects server addresses it cannot reach over the public internet.
Custom connectors sit on Grok's 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 Grok, append ?client=grok so SealGate tags the session as Grok in the dashboard:
https://mcp.sealgate.ai/mcp/<your-api-key>/?client=grokThe 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 Grok from the list - the dialog gives you a ready-to-copy URL with the ?client=grok tag already appended. (Alternatively, copy the base URL from the SealGate desktop app's Copy MCP URL menu and add ?client=grok 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=grok tag matters beyond the display label - SealGate relies on it to recognize Grok 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 Connector
Custom connectors are configured on your own Grok account, so each user's SealGate traffic is attributed to them - simply have every member add their own connection URL.
- Go to grok.com > Connectors (direct link:
https://grok.com/connectors). - Click New Connector, then select Custom.
- Under Transport, choose Streamable HTTP - SealGate's gateway speaks streamable HTTP.
- Paste your full connection URL from step 1 into the Server URL field, including the trailing slash and
?client=grok. - 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. Grok will connect and discover SealGate's tools.
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 Grok 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.