BlenderLens MCP Server

BlenderLens is an MCP integration. MCP server that lets AI agents build, check, preview and export game assets in Blender.

Packages and local setup

The published npm package is blenderlens-mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares 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- .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- .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 published pypi package is blenderlens-mcp, version 0.2.0. Its declared MCP transport is stdio.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related design & creative tools MCP servers for tools that cover the same kind of work.