Skip to main content
Glama
mohakmalviya

blender-compact-mcp

by mohakmalviya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to blender-compact-mcp

No user-submitted related servers found.

    Related Servers

    • Blender Universal & Token

      domainjon
      F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to inspect and drive Blender scenes directly, either through a live editor bridge on port 8190 or automatically via headless background CLI when Blender is closed. Provides token-efficient tools for scene outlining, object creation and modification, modifiers, materials, rendering, asset export, and arbitrary bpy script execution.
      11
      -

    • blender-mcp

      Mishaadevv
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.
      122
      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

    • bMCP

      niewinny
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to control Blender 3D through the Model Context Protocol, allowing Python execution, scene state queries, and automation of 3D workflows.
      5
      GPL 3.0
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct purpose: inspect reads Blender scene state, discover exposes the operation schema, execute mutates the scene via operations, and capture renders a preview. The read-side tools (inspect vs discover) are clearly separated as scene data versus API schema, so misselection is unlikely.

    Naming Consistency5/5

    All four tools use a consistent single-verb, lowercase snake_case convention (inspect, discover, execute, capture). There is no mixing of styles or noun/verb patterns, making the naming predictable.

    Tool Count5/5

    Four tools is well-scoped for a deliberately compact server, using a discover/execute dispatcher to cover many Blender operations without bloating the tool list. Every tool earns its place: read, schema, mutate, render.

    Completeness4/5

    The surface covers the core loop of discovering operations, executing them, inspecting results, and capturing previews, but lacks explicit save/export operations and relies on non-transactional partial execution. Capture is also limited to PNG stills rather than broader render outputs, though these are minor gaps workable via execute.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources