← Back to directory
B

Blender MCP Server

Community
Let any LLM control Blender 3D scenes in real time via structured JSON commands
GitHub source repository ↗
★ 96 Stars Category · Dev Tools Popular
37FMRS · D

An MIT-licensed community MCP server that bridges LLMs and Blender via a JSON-over-TCP protocol, offering real-time scene control and LLM-agnostic compatibility. The README does not enumerate specific tools or provide a client config example, so some details require checking its online documentation. Well suited for natural-language Blender workflows; not suitable for those needing official support or non-Blender pipelines.

Reliability
5/20
Security and permissions
8/20
Maintenance
9/20
Documentation
6/20
Setup experience
9/20
Read the FMRS scoring method →

Blender MCP is a plug-and-play Model Context Protocol server that lets any Large Language Model (GPT, Claude, or even local models) interact with Blender in real time using structured JSON commands over a TCP socket, enabling natural language control of 3D scenes. Maintained by pranav-deshmukh under the MIT License, it is a community project and not an official Blender product.

Setup

  1. Clone the repository: git clone https://github.com/pranav-deshmukh/blender-mcp.git and cd into it; 2. Install dependencies: pnpm install; 3. Start the MCP server: node index.js. Docs and demo at https://blender-mcp-studio.vercel.app/.

Fit and risk

Best for

  • 3D artists who want real-time LLM-driven scene control in Blender
  • Developers and hobbyists driving Blender via natural language
  • Users needing an LLM-agnostic integration (GPT, Claude, local models)

Not for

  • Users who do not work with Blender
  • Those seeking an officially supported Blender tool (this is community-built)
  • Users who need a GUI-driven workflow rather than command-based control

Required permissions

  • Requires network/socket access to send JSON commands over TCP
  • Requires read/write control over Blender scenes and objects

Risks and side effects

  • LLM-generated commands may unintentionally modify or damage the current Blender scene
  • TCP socket communication could be exposed on the local network if not secured
  • The README does not document authentication, so security hardening must be assessed independently

Troubleshooting

  1. Verify all dependencies were installed with pnpm install
  2. Check that node index.js starts the server without errors
  3. Confirm Blender is running and its connection settings match the TCP socket configuration
  4. Consult the usage docs at https://blender-mcp-studio.vercel.app/

Use cases

Control Blender 3D scenes with natural language
Full scene and object manipulation from code
Integrating Blender into MCP-enabled LLM workflows