Live data-center, power, grid and fiber intelligence, cited and machine-readable, inside Grok. It is one paste β the URL below is the whole install.
Paste this as your Grok MCP server URL
https://dchub.cloud/mcp?via=grok
An email is optional: it ties the key to you, so we can re-send it if you lose it, and we email a weekly summary of what your key looked up (only in weeks it is used; unsubscribe anytime).
Or copy the URL as it is: it works with no account, at the free daily limit.
Why bother: Grok runs MCP server-side and starts a brand-new session on every tool call, so it can never remember a key on its own. A key carried in the URL is the only thing that survives β without it you restart anonymous, at the anonymous limit, every single time.
Where it goes in Grok
grok.com β Connectors β New Connector β Custom
If the form also has an API key or authentication field, leave it empty. The key travels in the URL; a key in both places gets every call refused.
Save. The DC Hub tools register on your next message.
Prove it attached. Send this, verbatim: Use DC Hub. Which US grid has the most headroom right now? Confirm a get_grid_scoreboard call fires. If Grok answers from memory with no tool call, the connector is not attached.
Worth knowing. xAI: connectors are available to all Grok users; on Grok Business or Enterprise a team admin adds the connector first (console.x.ai β Grok Business β Connectors β Add Connector β Other). Grok runs MCP server-side and builds a new session for every tool call, so the connector URL is the only thing that persists. Its API-key field, where shown, sends nothing on its own (tested 2026-10-25), and the model cannot save anything for you.