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
      Not graded
      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.
      -

    • 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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clear, distinct concern: inspect reads scene state, discover exposes operation metadata, capture produces visual output, and execute runs operations. There is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency5/5

    All four tool names are single imperative verbs (inspect, discover, capture, execute), following a consistent and predictable style. The naming makes the toolset easy to scan and matches the compact design.

    Tool Count5/5

    Four tools is well-scoped for a compact Blender MCP server: read, discover, execute, and visualize are all core capabilities with no filler. The count fits comfortably in the ideal 3-15 range.

    Completeness5/5

    The toolset forms a complete workflow for controlling Blender: discover what operations exist, execute them, inspect the resulting scene, and capture a preview. Any remaining limitations are documented runtime behavior rather than missing lifecycle coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources