Harness Library
← Back to library

ViperMesh for Blender

A local Blender MCP workflow for building and checking 3D scenes.

3D & BlenderPackaged

Installation

Download MCP bundle ↓Source repository ↗

Version 1.3.0 · Focused MCPB server bundle. Install the separate Blender addon and optional source skill; the full mixed repository is not needed.

  1. Install and enable the Blender addon

    Download the addon from the release. In Blender, open Edit → Preferences → Add-ons → Install from Disk, select the downloaded Python addon file and enable ViperMesh for Blender. The maintainer currently tests Blender 5.2.

    Download Blender addon ↗

  2. Connect your MCP client

    Install Node.js 20+. Import the MCPB bundle into a client supporting local MCPB extensions. Keep the Blender viewport sidebar's ViperMesh Local Bridge running. Source-build/stdio configuration is documented in the repository for clients without MCPB import.

    Release, checksums and alternatives ↗

  3. Load the agent skill and start a session

    Read the skill plus its five relative reference files from the linked source folder. Copy the whole folder to your agent's documented skill location if desired. Have the agent bootstrap, inspect the existing scene and discover relevant operations before editing.

    Skill and reference folder ↗
    bootstrap_vipermesh_session
get_blender_agent_context
list_blender_tools

Manual setup

  • A local Blender session, enabled addon, and running Local Bridge are required. This is a local workstation connector, not a hosted Blender service.
  • MCP client needs stdio support; MCPB import is optional. The client should manage one persistent Node server process per agent session.
  • The addon listens on loopback 127.0.0.1:9876. The connector can change scene state and exposes code execution; use it with trusted agents and approved output paths.

Additional notes

  • Existing repository and release assets are listed unchanged. Nine top-level MCP tools route to a larger Blender operation registry; nine is not the total number of Blender operations.
  • The public connector and guidance are distinct from private studio capabilities and benchmark traces. Those are not included in this package.
  • Retain the source license and NOTICE.md when redistributing. Consult the upstream README for current supported Blender versions.