Data as of

BlenderMCP for Claude Code: Setup & Config

BlenderMCP links Claude Code to Blender for scene inspection, object and material changes, and Python execution.

BlenderMCP Claude Code configuration

  1. Choose Claude Code configuration scope

    For BlenderMCP, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

  2. Add BlenderMCP to Claude Code

    Use the blender-mcp entry below in mcpServers. Keep BlenderMCP's documented stdio connection fields and your other Claude Code entries.

  3. Check BlenderMCP in Claude Code

    BlenderMCP: Inspect claude mcp list and /mcp status.

Config file · Project scope: .mcp.json at the repository root

JSON
{
  "mcpServers": {
    "blender-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "blender-mcp"
      ],
      "env": {}
    }
  }
}

CLI (POSIX shell)
claude mcp add-json --scope project 'blender-mcp' '{"type":"stdio","command":"uvx","args":["blender-mcp"],"env":{}}'

BlenderMCP in Claude Code: stdio checks

  • If BlenderMCP fails to start, check uvx blender-mcp (from uv, for Python tools), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
  • BlenderMCP uses stdio here: Claude Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
Tools
get_scene_info, get_object_info, get_viewport_screenshot

BlenderMCP — details. Claude Code guide

Frequently asked questions

Register BlenderMCP with the displayed claude mcp add-json --scope project command, or merge the JSON into .mcp.json at the repository root.

Claude Code's blender-mcp example uses stdio.

BlenderMCP's Claude Code configuration invokes uvx blender-mcp (from uv, for Python tools).

BlenderMCP's stored list contains 17 tools, including get_scene_info, get_object_info, get_viewport_screenshot. Compare those names with Claude Code's connected tool list; the stored list is not a live check.