AgentHubAgentHub

Grok Build MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.Nuruvala/grok-build-mcp-server · v0.2.5

Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research. Grok Build is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHubDesign & creativeCursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-25
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Setup tutorial

  1. Open the Grok Build page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add grok-build-mcp-server -- npx -y grok-build-mcp-server

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "grok-build-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Grok Build

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Grok Build?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

Grok Build requires 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). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}
Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

Grok Build Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: grok_build_mcp_serverExecute the core tool interface of Grok Build
Request ArgumentsJSON Schema
{
  "target": "Grok Build",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

Grok Build + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

中文公文写作

v2.0.41

SkillClawHub10.2k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理，适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论，以及采购、整改、反馈和 AI 算力等场景。

source
View on ClawHub

Planning with files

v3.25.0

SkillClawHub45.4k

io.clawhub.othmanadi/planning-with-files

Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.

source
View on ClawHub

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: Grok Build
HTML
<a href="https://myagenthub.cn/p/io.github.Nuruvala/grok-build-mcp-server" title="Listed on AgentHub: Grok Build" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.Nuruvala/grok-build-mcp-server?lang=en" alt="Listed on AgentHub: Grok Build" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: Grok Build](https://myagenthub.cn/badge/io.github.Nuruvala/grok-build-mcp-server?lang=en)](https://myagenthub.cn/p/io.github.Nuruvala/grok-build-mcp-server)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.Nuruvala/grok-build-mcp-server",
  "type": "mcp-server",
  "version": "0.2.5",
  "displayName": "Grok Build",
  "description": "Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research.",
  "repository": {
    "url": "https://github.com/Nuruvala/grok-build-to-claude",
    "source": "github"
  },
  "homepage": "https://github.com/Nuruvala/grok-build-to-claude#readme",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "grok-build-mcp-server",
        "version": "0.2.5",
        "runtimeHint": "npx",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "GROK_BINARY",
            "description": "Path to the grok executable. Only needed when grok is not on PATH."
          },
          {
            "name": "GROK_MCP_PERMISSION_CEILING",
            "description": "Highest permission level any call may request. Granted once at registration and never prompts again."
          },
          {
            "name": "GROK_MCP_DEFAULT_PERMISSION",
            "description": "Permission level used when a call specifies none. Must be at or below the ceiling."
          },
          {
            "name": "GROK_MCP_DEFAULT_MODEL",
            "description": "Model used when a call omits one."
          },
          {
            "name": "GROK_MCP_DEFAULT_EFFORT",
            "description": "Reasoning effort used when a call omits one."
          },
          {
            "name": "GROK_MCP_TIMEOUT_MS",
            "description": "Wall-clock kill for a single run, in milliseconds."
          },
          {
            "name": "GROK_MCP_STATE_DIR",
            "description": "Directory for background job records. Defaults to $XDG_STATE_HOME/grok-mcp."
          },
          {
            "name": "GROK_MCP_MAX_CONCURRENT_RUNS",
            "description": "Background runs alive at once. Use off, none, or unlimited for no cap."
          },
          {
            "name": "STRUCTURED_CONTENT_ENABLED",
            "description": "Emit structuredContent alongside _meta. Off by default because some clients mishandle it."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.Nuruvala/grok-build-mcp-server",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.Nuruvala%2Fgrok-build-mcp-server/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}