Skip to content
Grok

three.ws Blender for Grok

io.github.nirholas/blender-mcp

Drive a local Blender headlessly: inspect, convert, render and script 3D files.

client:Grok transport:stdio runtime:npm

Install three.ws Blender in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen.

{
  "mcpServers": {
    "blender-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@three-ws/blender-mcp"
      ],
      "env": {
        "BLENDER_PATH": "<BLENDER_PATH>",
        "BLENDER_MCP_TIMEOUT_MS": "<BLENDER_MCP_TIMEOUT_MS>",
        "BLENDER_MCP_WORKDIR": "<BLENDER_MCP_WORKDIR>",
        "BLENDER_MCP_ALLOW_PYTHON": "<BLENDER_MCP_ALLOW_PYTHON>",
        "BLENDER_MCP_INLINE_IMAGE_BYTES": "<BLENDER_MCP_INLINE_IMAGE_BYTES>",
        "BLENDER_MCP_INLINE_IMAGE_PX": "<BLENDER_MCP_INLINE_IMAGE_PX>",
        "BLENDER_MCP_MAX_CONCURRENCY": "<BLENDER_MCP_MAX_CONCURRENCY>",
        "THREE_WS_BASE": "<THREE_WS_BASE>",
        "THREE_WS_FORGE_TIMEOUT_MS": "<THREE_WS_FORGE_TIMEOUT_MS>",
        "THREE_WS_FORGE_PROVIDER_KEY": "<THREE_WS_FORGE_PROVIDER_KEY>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

three.ws Blender in other clients