# ViperMesh for Blender [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Ker102/vipermesh-blender  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/vipermesh-for-blender

## Description
Free Blender MCP addon for faster AI scene edits, fewer tokens and built-in scene checks.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What ViperMesh for Blender MCP server does

ViperMesh for Blender MCP server links Blender with an AI assistant through the Model Context Protocol. It consists of a Blender addon and a Node-based MCP connector. After the addon starts its local bridge, a compatible client can send requests to work with the open Blender scene.

The project targets artists, hobbyists, and game creators who want assistance with 3D scene work. It is not an AI model inside Blender, and installing the addon alone does not provide an assistant. An MCP-compatible client is required to issue requests.

## How it works

The Blender addon runs inside Blender and provides the application-side connection. The MCP server is launched by the client as a stdio process, using either the packaged MCPB bundle or the built JavaScript entry point from a source checkout. Keep the Blender bridge running for the duration of the agent session.

Reusable actions handle many common operations without requiring the assistant to generate new Blender Python each time. The assistant can also inspect the scene, review images, and use custom Python for work that is outside the ready-made actions. This design is intended to reduce repeated setup and generated code for covered tasks, but token use and execution time still depend on the model and request.

## Setup and configuration

The currently tested release target requires Blender 5.2, Node.js 20 or newer, and an MCP client that supports stdio servers. Install the versioned addon Python file or ZIP from a release, then use Blender's Add-ons preferences to install and enable it. In the 3D Viewport sidebar, open ViperMesh and select **Start Local Bridge**.

For the connector, the packaged `v1.3.0` MCPB bundle can be imported into a client that supports local MCPB extensions. The bundle includes the Node server and dependencies, but the Blender addon and Node.js are still required. Alternatively, clone the repository, run `npm install`, and run `npm run build`. Configure the client to launch `dist/public-portable-blender-mcp.js` with Node from an absolute path. Do not launch `npm`, `npx`, or `tsx` for every individual operation.

## Tools and capabilities

ViperMesh for Blender provides ready-made actions for building, moving, duplicating, and arranging objects. Supported scene work described by the project also includes:

- Adjusting edge softness, materials, cameras, and lighting
- Checking object support, orientation, and available clearance
- Assisting with mesh cleanup, retopology, UV preparation, rigging, and weights
- Working with animation settings and preparing exports
- Inspecting results and using custom Python when an action is not covered

Scene checks can flag issues such as floating objects, incorrect orientations, and insufficient clearance. They help the assistant find and repair problems, but they do not guarantee an attractive or error-free scene.

## Limitations and notes

ViperMesh for Blender is a local connector, not a hosted Blender service. The public addon does not include private ViperMesh Studio asset libraries. The examples in the project describe possible requests rather than bundled scene templates.

The connector is built on the original MCP for Blender project, but its stated focus is reusable editing actions and scene checks instead of newly generated Python for routine changes. Both approaches can inspect scenes and run custom Python; the available features and workflow differ. Results vary by task, model, assets, and the state of the Blender scene. The bridge must remain active while the agent is working.

_Full upstream README: https://allmcps.com/mcp/vipermesh-for-blender/readme_