Blender MCP
Drives Blender on your own isolated desktop or VM — scene inspection, object and material edits, Python execution, and asset imports. Needs a running Blender session with the addon plus an authenticated HTTPS MCP bridge.
What it provides
Connect an existing HTTPS deployment, with a scoped token where the service requires one. Heavy jobs stay on that service instead of using bot memory.
Connection requirements
Run Blender, its BlenderMCP addon, and `uvx blender-mcp` together on an isolated desktop or VM, and leave the addon port 9876 bound to loopback. Bridge the stdio server to Streamable HTTP (`supergateway --stdio "uvx blender-mcp" --outputTransport streamableHttp`) and publish /mcp through a TLS proxy that ENFORCES the bearer token, because the bridge only forwards headers and adds no access control of its own. Keep the bridge running as a service: a cold `uvx` start downloads dependencies and can outlast the 120s call deadline. Treat the connection as remote code execution — execute_blender_code runs generated Python with the Blender user’s full permissions, so keep only disposable .blend copies on that machine. Asset and 3D-generation tools (Poly Haven, Sketchfab, Poly Pizza, Hyper3D, Hunyuan3D) need their own keys and are billed by those services, not by us.
- Protocol
- Streamable HTTP MCP
- Endpoint
https://blender-mcp.example.com/mcp- Authentication
- bearer
mcp call get_addon_status {}mcp call get_scene_info '{"user_prompt":"inspect my scene"}'Where to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.