Build and arrange
Assembly, transforms, materials, cameras and lighting. Discover the tools your task needs, then operate on named objects.
Geometry / Materials / Scene
-
- Open source / MIT licensed / Local
ViperMesh
for Blender
Give your agent
the tools to work in 3D.
Connect an MCP-compatible agent to Blender. Inspect your scene, make structured edits and check the result through one persistent session.
+ Your scene. Your agent.
+
+ Open-source Blender MCP
+Your scene. Your agent.
ViperMesh for Blender.
+ A direct connection between your AI agent and Blender.
Structured edits, scene inspection and room for custom work.
+ Get started
+ Download addon
+
+ MIT licensedRuns locallyNo ViperMesh account
+
+
+
+
+
+
+ Example MCP sessionstdio loopback
+ -
+
- 01
bootstrap_vipermesh_sessionConnect
+ - 02
call_blender_tool("get_scene_info")Inspect
+ - 03
run_blender_scene_stageBuild & review
+
An agent connection for your existing workspace
Structured operations
Assembly, transforms, materials, cameras, lighting, rendering, UVs, retopology, rigging and export. Discover relevant tools as the task develops.
Inspect, then improve
Check support, orientation and clearances. Review visual results and repair specific problems. Diagnostic checks support judgment; they cannot certify every scene.
Room for custom work
Keep Python execution for unusual geometry and uncovered operations. Batch known actions and keep decision points where new observations matter.
One session. One local connection.
Your MCP client→ViperMesh server→Blender addon
The client launches the Node server once. The server keeps a serialized connection to the addon. No ViperMesh cloud account or Docker is needed for the local connector.
From download to first edit
Connect your agent.
Use the Blender version currently tested in the repository and a Node runtime that meets the package requirements. Keep Blender open with the local bridge running.
Client-specific setup and troubleshooting ↗Install the addon
Download the versioned addon
.pyor.zipfrom the latest release. In Blender, install it from disk, enable it, and start the local bridge in the ViperMesh sidebar.Build the MCP server
git clone https://github.com/Ker102/vipermesh-blender.git ++ ++Less boilerplate. More scene work.
Tools for the work
between idea and result.Use structured operations for familiar tasks.
Keep Python for the ones that need it.+++ Inspect and refine
Check support, orientation and clearances. Review render images and repair specific problems before accepting the result.
Spatial checks / Visual reviewKeep custom work open
Retain Python execution for unusual geometry and uncovered operations. Batch known actions; pause when a decision needs new evidence.
Python fallback / Bounded batches+Also includes
- UV preparation
- Retopology
- Rigging
- Weight tools
- Animation operations
- Export checks
+ ++++A small bridge. A persistent connection.
Keep your agent
close to your scene.++Your MCP clientStarts one Node server+ +ViperMesh serverOne serialized connection+ +Blender addonLocal bridge on 127.0.0.1+No hosted ViperMesh service is required. Docker is optional, not part of the standard local setup.
++ ++From download to first edit
Make the connection.
Install the addon, point your MCP client at the server, and keep Blender open while your agent works.
Tested target: Blender 5.2
Client-specific setup
Node.js 20 or newer · stdio-compatible MCP client-
+
- 01
Install the Blender addon
Download the versioned
.pyor.zipfrom the latest release. Install it from disk in Blender, enable it, then start the local bridge in the ViperMesh sidebar.
+ - 02+
Build the MCP server
++git clone https://github.com/Ker102/vipermesh-blender.git cd vipermesh-blender npm install -npm run buildAdd it to your MCP client
Configure the client to launch
nodewith the absolute path todist/public-portable-blender-mcp.js. Start one server per session, not one per tool call.{ +npm run build
+ - 03
Configure your MCP client
Launch
+nodewith the absolute path to the built server. This JSON is a common configuration pattern; your client's syntax may differ.++{ "mcpServers": { "vipermesh-blender": { "command": "node", "args": ["/absolute/path/to/vipermesh-blender/dist/public-portable-blender-mcp.js"] } } -}JSON configuration above is a common pattern; your client's syntax may differ.
Inspect before editing
Ask your agent to call
bootstrap_vipermesh_session, inspect the existing scene, then discover tools for your task. The repository includes a portable agent skill with adaptable operating guidance.What to expect
Is it a 3D generation model?
The connector lets an agent operate Blender. It does not bundle a hosted text-to-3D model or promise production-ready assets. You can use local assets and your own Blender workflows.
Is it faster than UI automation?
Structured tools are designed to avoid repetitive navigation and generated Blender code. Performance depends on the model and task; we are preparing reproducible comparisons and make no universal speed or cost claim here.
Does it judge the final scene automatically?
Tools provide diagnostics and image-file checks. The agent still needs to inspect visual output and judge it against your request. A passing report can miss mesh-level collisions or an artistic mismatch.
What can an agent access?
This is a trusted local connector. Python fallback can execute arbitrary code inside Blender. Keep the bridge on loopback, connect trusted clients and review destructive actions. Read the repository security guidance before use.
How does this relate to ViperMesh Studio?
The public connector is usable independently. ViperMesh Studio is a broader AI workspace in development for artists and game creators, connecting generation, inspection and specialist workflows.
Join the Studio waitlist ↗Start with your scene.
Try one useful edit. Inspect the result. Tell us where the connection helps and where it falls short.
Share feedback ↗
+ - 04
Start with an inspection
Call
Install the portable agent skillbootstrap_vipermesh_session, inspect the scene, then discover the capabilities needed for your task. Keep the server running for the whole session, not one process per call.
+
+ ++Clear scope. Fewer surprises.
Know what you're connecting.
+Is this a 3D generation model?
The connector lets an agent operate Blender. It does not bundle a hosted text-to-3D model or promise production-ready assets. Use your own assets and Blender workflows.
+Is it faster than UI automation?
Structured tools avoid repetitive UI navigation and generated code for covered operations. Performance still depends on the model and task. No universal speed or cost claim is made here.
+Does it automatically judge the final scene?
Tools provide diagnostics and image-file checks. The agent still needs to inspect the visual output against your request. Bounds-based reports can miss mesh collisions or an artistic mismatch.
+What can an agent access?
This is a trusted local connector, not a sandbox. Python fallback can execute arbitrary code inside Blender. Keep the bridge on loopback, use trusted clients, and review destructive actions.
Read the security guidance+Where does ViperMesh Studio fit?
The public connector works independently. Studio is a broader artist-controlled AI workspace in development, bringing generation, asset inspection and specialist workflows together.
Join the Studio waitlist+ +Share feedbackBuild it with us
Start with your scene.
Try a useful edit. Inspect the result.
Tell us what works and what needs a better tool.