Use MCP servers in Grok Build with Toolport
Toolport is a free, open source local MCP gateway. Add your servers to Toolport once, flip the Grok Build toggle, and Grok Build gets all of them through a single gateway entry, with lazy discovery loading a handful of meta-tools instead of every server's full tool list.
Setup
- Download Toolport for Windows, macOS or Linux, and add your MCP servers to it (or import the ones your other AI agents already have; secrets go to your OS keychain).
- Open the Clients tab and toggle Grok Build on. Toolport writes its gateway entry into Grok Build's config, next to anything already there.
- Restart or reload Grok Build. Your full server set is available through Toolport, and any server you add later shows up without touching Grok Build again.
Where Grok Build keeps its MCP config
- All platforms
~/.grok/config.toml
TOML with [mcp_servers.<name>] tables, the same shape Codex uses.
Good to know
- Set GROK_HOME to relocate the config directory and Toolport follows it, the same way it follows CODEX_HOME for Codex.
Why a gateway instead of Grok Build's own server list?
- One setup, every agent. The same servers work in Grok Build and every other AI agent on your machine; add a server once and they all get it.
- Up to 91% fewer tool tokens. Instead of every server dumping its tool list into context, the agent loads a handful of meta-tools and searches on demand (measured).
- Secrets in the OS keychain. API keys are injected at runtime and never sit in Grok Build's config file.
- Watched by default. Rug-pull and tool-poisoning detection on every tool, plus per-tool governance and a destructive-tool kill switch. How the security works.