ViperMesh for Blender

Free, open-source Blender MCP server

Make more. Wait less.
ViperMesh for Blender.

Connect your AI assistant to Blender with the ViperMesh MCP server and addon.
Reusable tools for scene edits, inspection and 3D workflows.

Get started Download addon

MIT licensedRuns locallyNo ViperMesh account

Example MCP sessionstdio loopback
  1. 01bootstrap_vipermesh_sessionConnect
  2. 02call_blender_tool("get_scene_info")Inspect
  3. 03run_blender_scene_stageBuild & review
Less generated code. Your scene stays in Blender.

For artists, hobbyists and game creators

AI help for your
next Blender scene.

Build, arrange and refine objects with your AI assistant.
Spend more time on the result, less on the steps to get there.

Use fewer AI tokens

Give your assistant ready-made actions for placement, materials, lighting and more. Covered edits need less newly generated Blender code.

Reusable actions   /   Less code to generate

Keep work moving

The connection stays open, and related edits can run together. Your assistant has simpler ways to act, with less repeated setup and back-and-forth.

One connection   /   Related edits together

Get better-checked results

Help your assistant catch floating objects, wrong orientations and spacing problems. Inspect the scene, review the image and fix what is off.

Scene checks   /   Visual review

Also helps with

  • UV preparation
  • Retopology
  • Rigging
  • Weight tools
  • Animation operations
  • Export checks
See all Blender tools

A 72-second introduction

How the connection works.

Your request, ready-made Blender actions, and a result you can inspect.

Silent illustrated overview, not a recorded benchmark. Actual time and token savings depend on the task and your AI model.
Download MP4 Connect your assistant
Read the overview

Send your goal in a compatible AI client. The assistant selects a ViperMesh tool and applies the edit in Blender. Common operations use object names and settings rather than newly generated editing code. Tools cover arrangement, materials and lighting, geometry and UV preparation, scene inspection, and export. Custom Python remains available for unusual work. The assistant still needs to check the result, including support, clearance and the rendered view. Reusing operations can reduce code generation and repair overhead; total savings vary. Install the free addon, connect your existing AI client, then work in Blender. AI provider access and token tracking are separate from the connector.

A real Blender scene comparison

One reference.
Two Blender workflows.

Reference image, ViperMesh MCP, and the original BlenderMCP baseline.

Historical comparison showing the reference room on the left, ViperMesh MCP's Blender viewport in the centre, and the original BlenderMCP viewport on the right
From a historical scene-reconstruction test. Only the centre heading was relabelled; the reference and scene pixels are unchanged. One example, not a universal quality claim.

The benchmark used its own guidance and available assets. The public addon does not bundle private Studio asset libraries.

Read the case study, Part One Full-size comparison

Your assistant. Your Blender workspace.

Ask for an edit.
Keep creating in Blender.

Your AI assistantIn an app that supports MCP
ViperMesh connectionReady-to-use Blender actions
Your Blender sceneOn your own computer

No ViperMesh account or hosted ViperMesh service is required. Your AI app may have its own costs. Docker is not needed for the standard local setup.

From download to first edit

Connect your assistant.

Install the addon and connect your AI app using the steps below. You do not need to write Python for covered edits, but the initial setup is not yet one-click.

Tested target: Blender 5.2
Node.js 20 or newer · AI app with stdio MCP support

Setup for your AI app
  1. 01

    Install the Blender addon

    Download the versioned .py or .zip from the latest release. Install it from disk in Blender, enable it, then start the local bridge in the ViperMesh sidebar.

  2. 02

    Install the MCP connection

    Download the MCPB bundle and import it into a compatible client. Node.js and the Blender addon are still required. See bundle setup and validation limits. Prefer the source route? Use these commands:

    Terminal
    git clone https://github.com/OpenRootdev/vipermesh-blender.git
cd vipermesh-blender
npm install
npm run build
  3. 03

    Configure your MCP client

    Launch node with the absolute path to the built server. This JSON is a common configuration pattern; your client's syntax may differ.

    MCP configuration
    {
  "mcpServers": {
    "vipermesh-blender": {
      "command": "node",
      "args": ["/absolute/path/to/vipermesh-blender/dist/public-portable-blender-mcp.js"]
    }
  }
}
  4. 04

    Start with an inspection

    Call bootstrap_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.

    Install the portable agent skill

Clear scope. Fewer surprises.

Know what you're connecting.

What is a Blender MCP addon?

MCP means Model Context Protocol: a standard that lets compatible AI assistants use tools in an application. ViperMesh connects your assistant to Blender so it can inspect and edit your scene. The addon alone does not include an AI model.

How does it compare with the original BlenderMCP?

ViperMesh builds on the original community project with a focus on reusable editing actions and scene checks. Both can inspect scenes and run Python. ViperMesh gives assistants ready-made tools for common edits, aiming to reduce generated code, save time and make results easier to check.

Read the comparison
Does it always use fewer tokens or give better results?

That is the design goal, not a guarantee for every task. Ready-made actions can reduce generated code and repeated steps. Tokens are the units of text an AI model reads and writes; total usage and final quality depend on your model, scene and request.

Do I need to be a programmer?

You can ask for covered scene edits in ordinary language without writing Python yourself. Import the MCPB bundle in a supported client, or build from source. You still need the separately enabled Blender addon, Node.js and a configured AI app. Custom requests may lead your assistant to use Python, which you should review when appropriate.

Is this a 3D generation model?

The addon lets an assistant operate Blender. It does not bundle a hosted text-to-3D model or promise production-ready assets. Use your own assets and Blender workflows.

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

Install the Blender MCP connection.

ViperMesh has two local parts: an addon running in Blender and an MCP server started by your AI client. The server uses stdio; the addon listens on a loopback bridge.

Read the full installation and troubleshooting guide

ViperMesh in Harness Library ยท Documentation for agents

Build it with us

Start with your scene.

Try a useful edit. Inspect the result.
Tell us what works and what needs a better tool.

Share feedback