Skip to main content
Glama
Sign In
ViperMesh for Blender

ViperMesh for Blender

by OpenRootdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ViperMesh for Blender

No user-submitted related servers found.

    Related Servers

    • Blender MCP

      jagathgj
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Blender to AI assistants through the Model Context Protocol, enabling direct AI control of 3D modeling, scene creation, and manipulation via natural language.
      MIT

    • BlenderMCP

      omniconnexsynapse
      A
      license
      B
      quality
      C
      maintenance
      Connects Blender to AI through the Model Context Protocol to enable prompt-assisted 3D modeling and scene manipulation. It supports object creation, material control, and arbitrary Python code execution directly within the Blender environment.
      22
      MIT

    • Blender-MCP

      Aayushdubey101
      A
      license
      A
      quality
      D
      maintenance
      Connects Blender 3D to AI assistants via the Model Context Protocol, enabling natural language driven 3D scene creation, manipulation, and rendering.
      15
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: connection checking, tool listing, single calls, batch calls, scene staging, and guidance retrieval. There is some overlap between bootstrap_vipermesh_session, check_blender_connection, and get_blender_agent_context because bootstrap combines connection checking and context loading, but the descriptions clarify when each should be used.

    Naming Consistency5/5

    All tool names use consistent snake_case and follow a verb_noun pattern such as check_blender_connection, call_blender_tool, and get_3d_guidance_document. Domain-specific terms like blender and 3d are applied predictably across the set.

    Tool Count5/5

    Nine tools is well-scoped for a Blender MCP gateway that needs session setup, connection checking, tool discovery, command execution, batching, scene staging, and guidance access. Each tool appears to earn its place without excessive surface area.

    Completeness4/5

    The surface covers the main lifecycle: session bootstrap, connection verification, tool discovery, single and batch command execution, scene workflow staging, and guidance lookup. Minor gaps exist, such as no explicit session teardown or direct tool-schema introspection, but the generic call path can likely work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources