Blender through MCP

This package launches Blender Lab's MCP server. Installing it changes nothing on the computer: you open Blender when a task needs it, and install Blender or Blender Lab's add-on only after the user agrees. A successful MCP tool listing proves server startup, not a connection to Blender.

Getting Blender ready

Make Blender ready yourself instead of asking the user to open it. Do this before the first scene call of a task, and again whenever a scene call cannot connect.

Find Blender once and use that installation for every step below. Pick the newest version of 5.1 or later (<blender> --version prints it) from:

• Linux: blender on PATH; ~/.local/opt/blender-*/blender (where you install it); flatpak org.blender.Blender (run it as flatpak run org.blender.Blender); snap /snap/bin/blender; Steam ~/.steam/steam/steamapps/common/Blender/blender, ~/.local/share/Steam/steamapps/common/Blender/blender or ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Blender/blender.
• macOS: Blender.app in /Applications, ~/Applications or ~/Library/Application Support/Steam/steamapps/common/Blender/. Its executable is <Blender.app>/Contents/MacOS/Blender.
• Windows: blender on PATH; the folder of the Blender entry in the uninstall registry; $env:ProgramFiles\Blender Foundation\Blender <version>\blender.exe; $env:LOCALAPPDATA\Programs\Blender Foundation\blender-*\blender.exe (where you install it); the Microsoft Store package, whose Version and InstallLocation (holding blender.exe) come from Get-AppxPackage BlenderFoundation.Blender.

None found, or only versions older than 5.1: see Installing Blender.

<blender> below is that executable (on Windows, call it as & "<blender>" ... in PowerShell, since the path has spaces). The short checks below (--command extension list, --command blender_mcp --help, --python-expr) exit on their own and are not a second Blender window; the headless bridge in step 6 keeps running until stopped.