Skip to main content
Glama
behlulgoker

BlenderMCP

by behlulgoker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to BlenderMCP

No user-submitted related servers found.

    Related Servers

    • BlenderMCP

      Eminemminem
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, and manipulation through natural language commands.
      17
      2
      MIT

    • BlenderMCP

      KorwinTeo
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender 3D to Claude AI through the Model Context Protocol, enabling prompt-driven 3D modeling, scene creation, and real-time object manipulation.
      22
      MIT

    • BlenderMCP

      mikeysrecipes
      A
      license
      B
      quality
      D
      maintenance
      Connects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation.
      17
      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

    A3.7/5.0

    Scored across 22 tools

    Disambiguation4/5

    The tools split cleanly by integration/provider (Hyper3D, Hunyuan3D, Sketchfab, Polyhaven) and action (status, generate, poll, import, search, download), so most are easy to tell apart. However, the multiple generation tools and the two import_generated_asset variants have overlapping shapes and could be misselected without careful reading.

    Naming Consistency4/5

    Most tools follow a consistent get_/generate_/poll_/download_/search_ + noun pattern, and all are snake_case. The main inconsistency is that Hunyuan tools use 'hunyuan3d'/'hunyuan' while Hyper3D tools mix 'hyper3d' and 'rodin', and the import functions are named asymmetrically.

    Tool Count3/5

    At 22 tools, this is on the heavy end for an MCP server, and the count feels borderline even though the breadth is somewhat justified by three large asset integrations plus scene inspection. Each tool has a real purpose, but the overall surface could be tightened.

    Completeness4/5

    The asset lifecycle is well covered: check integration, generate/search, poll, import/download, plus scene observation and arbitrary code execution for fallback. Minor gaps include no direct update/delete operations for imported assets and no dedicated Sketchfab model detail retrieval beyond preview, but these are workable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources