Blender MCP (Node.js)
A small Node.js Blender MCP: a stdio server sends Python code to Blender over TCP, reads the scene and pulls Poly Haven assets
- 98 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent sends arbitrary Python code to Blender and it runs with the permissions of your Blender
- The add-on listens on a TCP port on the local machine and accepts commands without checking the sender
Install
- Works in
Manual install
git clone https://github.com/pranav-deshmukh/blender-mcp.git && cd blender-mcp && pnpm install && node index.jsCommands from the project description. The addon/simple_mcp_addon.py add-on is installed separately in Blender.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent sends arbitrary Python code to Blender and it runs with the permissions of your Blender
- The add-on listens on a TCP port on the local machine and accepts commands without checking the sender
This is third-party code. Review the repository files before installing.
What it does
The project has two parts. The index.js server on Node.js is built on the official MCP SDK and talks to the client over stdio. The simple_mcp_addon.py add-on runs inside Blender 4.3 or newer, listens on local TCP port 8765 and shows an MCP panel in the 3D view sidebar. The agent gets the tools send-code-to-blender, test-blender-connection and fetch-scene-from-blender. The first sends Python code to run in Blender, the second checks the link with a test command, the third returns the scene name and a list of objects with type, location and dimensions. A request to Blender waits five seconds for an answer. Separate tools work with the Poly Haven catalog: the server asks its API for asset types, and the add-on downloads a .blend file with textures into a temporary folder and imports it into the scene.
Who it is for. For developers who want to understand how an MCP-to-Blender bridge works or take a minimal base for their own Node.js server.
Good fit when
- You want a Blender MCP in Node.js rather than Python so you can extend it in a familiar stack
- The agent needs a list of scene objects with types, locations and dimensions
- A Poly Haven asset with textures should be pulled into the scene on request
- You are studying the protocol: the code is short and commands travel as plain JSON over TCP
- You need a minimal base to add your own tools without someone else's abstractions
Not a fit when
- You want a ready package with one-command install: here you clone the repository and run node index.js
- You need dedicated tools for materials, animation and rendering: there are none, only sending Python code
- Port 8765 is taken by another service: it is hard-coded
- You need an actively maintained project: the repository's last update is from August 2025
Example request
Test the connection to Blender, get the scene's object list, then find a suitable tree asset on Poly Haven and add it to the scene.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
This is a small project with no package registry and no ready client configuration: the description only shows node index.js after pnpm install, and you add the entry to your MCP client settings yourself. Port 8765 and the localhost host are set in code. A detailed tool description is on the project site, while the repository itself has little documentation. The license is MIT. Use from Russia was not checked: the server is local, but the Poly Haven catalog is requested over the network.
How to disable. Remove the server entry from the MCP client config and disable the Simple MCP Receiver add-on in Blender preferences.
FAQ
How do I install the Node.js Blender MCP?
Clone the repository, run pnpm install and start node index.js. Install the addon/simple_mcp_addon.py add-on in Blender separately and turn on command intake in the MCP panel.
Which Blender version does this Blender MCP need?
The add-on declares compatibility with Blender 4.3 and newer. The server connects to it over local TCP port 8765.
What tools does this server have?
send-code-to-blender runs the Python code you send, test-blender-connection checks the link, fetch-scene-from-blender returns the scene objects. There are also Poly Haven tools for asset types and downloads.
How does it differ from a Python Blender MCP?
The server here is written in Node.js and kept small: no uvx package and no ready tools for materials or animation, only code, scene and Poly Haven.
Does it work only with Claude?
No. The project calls itself model-agnostic and lists GPT, Claude and local models, because communication goes over plain MCP.
Discussion
No questions or reviews yet.
Related
MCP serversBlender MCP
MCP for Blender
An MCP server and Blender addon: the agent creates and edits objects, materials and scenes, pulls assets and runs Python in Blender
An enhanced Blender MCP build: work with a live Blender and with saved .blend files without a UI, runtime bpy API lookup and the BlenderBench test suite
Blender MCP: an agent in Cursor, Cline, Windsurf or Claude Desktop builds and edits 3D scenes in Blender from a description; the server installs with uvx
An MCP server for Ableton Live: the agent creates tracks, places clips and builds arrangements straight in the open project
An MCP server for Windows that drives an installed Photoshop: documents, layers and arbitrary JSX scripts
MCP server that drives local Adobe Premiere Pro projects from Claude, Codex and other MCP clients
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Blender MCP (Node.js) (this entry) | no | not required | 98 | |
| Blender MCP | no | not required | 32,624 | another Blender MCP server with its own add-on |
| Blender Skills | no | 1,347 | Blender skills for agents rather than a Node.js server |
README in short
The description is short: the server lets any language model control Blender in real time through JSON over a TCP socket. It claims real-time exchange, a clean protocol structure, full scene control from code and model independence. Installation takes three steps: clone, install dependencies, start the server. Documentation and a demo live on a separate site.