Grok Build MCP Server

What this does

Grok Build exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

GROK_BINARY
GROK_MCP_PERMISSION_CEILING
GROK_MCP_DEFAULT_PERMISSION
GROK_MCP_DEFAULT_MODEL
GROK_MCP_DEFAULT_EFFORT
GROK_MCP_TIMEOUT_MS
GROK_MCP_STATE_DIR
GROK_MCP_MAX_CONCURRENT_RUNS
STRUCTURED_CONTENT_ENABLED

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Grok Build?

Run the Claude Code command in the install section to add Grok Build to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Grok Build?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Grok Build as well.

Does Grok Build need an API key?

This listing does not flag an API key as required. The server can use these environment variables: GROK_BINARY, GROK_MCP_PERMISSION_CEILING, GROK_MCP_DEFAULT_PERMISSION, GROK_MCP_DEFAULT_MODEL, GROK_MCP_DEFAULT_EFFORT, GROK_MCP_TIMEOUT_MS, GROK_MCP_STATE_DIR, GROK_MCP_MAX_CONCURRENT_RUNS, STRUCTURED_CONTENT_ENABLED; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.