Skip to main content
Glama
RoxyCoding

Roxy Blender MCP

by RoxyCoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Roxy Blender MCP

No user-submitted related servers found.

    Related Servers

    • mcp-for-blender

      clanker25
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven 3D modeling and scene creation in Blender, allowing LLMs to create, modify, and manipulate objects, materials, and assets through natural language.
      31
      MIT

    • Blender-Mind-MCP

      xiaohai-uid
      A
      license
      A
      quality
      C
      maintenance
      Enables AI-driven 3D modeling in Blender by providing tools to create primitives, apply modifiers and materials, set up lighting and cameras, capture viewport snapshots, export assets, inspect scenes, and execute Python commands via natural language.
      10
      MIT

    • BlenderMCP

      IAmMarcellus
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude AI to directly control Blender for automated 3D modeling, scene creation, and object manipulation. It provides tools for material management, scene inspection, and integration with third-party asset libraries like Poly Haven and Sketchfab.
      10
      2
      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.2/5.0

    Scored across 58 tools

    Disambiguation3/5

    With 58 tools, several clusters overlap—quality checks (review_model vs analyze_quality, check_contacts vs inspect_connections), import/export variants (import_asset vs import_model_file, export_model vs export_skeletal vs make_game_asset), and capture tools (look vs viewport_screenshot). The verbose descriptions explicitly distinguish them, but the sheer number and proximity of related operations will still force careful reading to avoid misselection.

    Naming Consistency4/5

    Tool names are overwhelmingly snake_case with verb_noun or noun_verb patterns, and prefixes like create_*, add_*, setup_*, uv_*, rig_*, export_*, import_* are used consistently. A handful of single-word verbs (look, scatter, animate, batch) and noun-first names (viewport_screenshot, modeling_progress) are minor deviations.

    Tool Count1/5

    58 tools far exceeds the typical 3–15 well-scoped range and even the 25+ 'too many' threshold, placing it in extreme mismatch territory for a single MCP server. Although each tool has a specialized role, the cognitive load and selection risk are very high.

    Completeness5/5

    The surface covers the full 3D lifecycle: scene inspection, primitive and advanced mesh creation, editing, modifiers, materials, UV, lighting, camera, rendering, procedural detail, animation, prop/character rigging, game-asset baking/export, asset libraries, and quality analysis. execute_python also acts as an escape hatch, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources