BlenderLens MCP Server

What the code does

We read the source, 4 d ago · rules ccca72095570

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

  const child = spawn(found.command, [...found.prefix, ENTRY_POINT, ...process.argv.slice(2)], {

            target = os.path.join(cells_folder, f"{index}.png") if sheet else path

            exec(compiled, namespace)

        result = subprocess.run(command)

    env = dict(os.environ, BLENDERLENS_SESSION_TOKEN=token)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add blenderlens -- npx -y blenderlens-mcp

{
  "mcpServers": {
    "blenderlens": {
      "args": [
        "-y",
        "blenderlens-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.blenderlens]
command = "npx"
args = ["-y", "blenderlens-mcp"]

{
  "mcpServers": {
    "blenderlens": {
      "args": [
        "-y",
        "blenderlens-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "blenderlens": {
      "args": [
        "-y",
        "blenderlens-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: BLENDER_BIN (Blender executable, for background sessions, install-addon, and the check command on a .blend; found on PATH or in the usual install folders when unset), BLENDERLENS_MODE (auto (the Blender window running the add-on if it responds, otherwise a background Blender), live, or background), BLENDERLENS_HOST (The address the server connects to for the BlenderLens add-on in live mode), BLENDERLENS_PORT (The add-on's port, as set in its preferences), BLENDERLENS_TOKEN (Overrides the token the server reads from the add-on's connection file (live-<port>.json)), BLENDERLENS_TIMEOUT (Seconds to wait for one call; render_preview, run_python, run_script and bake_texture also take a timeout of their own), BLENDERLENS_START_TIMEOUT (Seconds to wait for a background Blender to come up), BLENDERLENS_RENDER_DIR (Where render_preview writes when given no path. When unset, blenderlens/renders in the system temp folder, where previews older than 7 days are removed when the server starts), BLENDERLENS_ALLOW_PYTHON (0 leaves run_python and run_script out of the tool list and refuses them (not_allowed)), BLENDERLENS_ALLOWED_DIRS (Folders that every path given to a tool must lie inside, separated by ; on Windows and : elsewhere. render_preview may also write to its render folder (BLENDERLENS_RENDER_DIR). When unset, paths are not confined), BLENDERLENS_RUNTIME_DIR (Where the add-on writes live-<port>.json for the server, and where recovery copies go; Blender and the server must agree. Default: %LOCALAPPDATA%\blenderlens on Windows, ~/Library/Application Support/blenderlens on macOS, and $XDG_STATE_HOME/blenderlens or ~/.local/state/blenderlens elsewhere). The author declared them in the registry entry; get the values from the project itself.