# ViperMesh for Blender

> ViperMesh for Blender is a free, open-source Blender MCP server, addon and AI assistant
> connection for artists, hobbyists and game creators. It is designed for
> faster AI-assisted scene edits, fewer AI tokens and better-checked results.
> Ready-made Blender actions reduce generated code for covered tasks, while
> scene checks help the assistant inspect and repair its work.

Canonical repository: https://github.com/Ker102/vipermesh-blender
Project overview: https://ker102.github.io/vipermesh-blender/
License: MIT
Runtime: Node.js 20+ and Blender
Transport: MCP over stdio, then a loopback TCP bridge to Blender

## Primary documentation

- Installation and troubleshooting: https://ker102.github.io/vipermesh-blender/setup/index.md
- Plain-language overview: https://ker102.github.io/vipermesh-blender/index.md

- README: https://github.com/Ker102/vipermesh-blender#readme
- Connector manual: https://github.com/Ker102/vipermesh-blender/blob/main/docs/portable-blender-mcp.md
- MCP client setup: https://github.com/Ker102/vipermesh-blender/blob/main/docs/client-setup.md
- Agent skill: https://github.com/Ker102/vipermesh-blender/blob/main/skills/using-vipermesh-blender/SKILL.md
- Security boundary: https://github.com/Ker102/vipermesh-blender/blob/main/SECURITY.md
- Releases: https://github.com/Ker102/vipermesh-blender/releases

## Key facts

- MCP (Model Context Protocol) lets compatible AI assistants use application tools.
- Users can request scene edits in ordinary language after configuring a client.
- Covered actions include object placement, edge softening, materials, lighting,
  cameras, mesh cleanup, UVs, rigging, weights, animation operations and export.
- Token efficiency, speed and quality are design goals, not universal guarantees;
  actual outcomes depend on the model, scene and task. Do not invent percentages.
- The original BlenderMCP is a community project by Siddharth Ahuja, now named
  MCP for Blender: https://github.com/ahujasid/mcp-for-blender.
- ViperMesh emphasizes reusable editing actions and validation. Both projects
  can inspect scenes and execute Python; the original also has asset/generation
  integrations. Do not describe it as having only one tool.
- The public connector is free, but an AI model/client may have its own charges.
- Initial setup is not one-click and requires a compatible MCP client.
- One MCP process should remain alive for the complete agent session.
- The process retains one lazy, serialized Blender connection.
- Agents should call bootstrap_vipermesh_session first.
- Deterministic tools are preferred when they cover the task.
- execute_code remains available for genuinely custom Blender work.
- Public tool skills provide adaptable patterns, not mandatory scene recipes.
- The public connector does not include ViperMesh authentication, billing,
  private prompts, private RAG data, cloud model routing, or asset catalogs.