Skip to main content
Glama

Related Servers

Alternatives to blender-mcp-master

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to control Blender for modeling, materials, animation, physics, rendering, scene inspection, documentation search, and asset/generation service integration. It exposes a stdio endpoint with many Blender operations for creating and editing 3D content.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive a live Blender session over stdio, inspecting the scene graph, searching and calling operators, reading and writing RNA properties, rendering viewable images, and checkpointing or restoring the file across a multi-turn conversation. It also exposes gallery and scene-reset helpers so the agent can check its own work and start over cleanly.
      19
      GPL 3.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to control Blender through its official MCP add-on: running arbitrary bpy code or background CLI jobs, auditing scenes and blend files, searching Blender API and manual docs, capturing screenshots and renders, and searching or importing free Poly Haven models, HDRIs and textures at real-world scale. All 28 tools are served over one stdio connection to a single Blender instance.
      28
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP hosts to list and render bundled prompt templates and fetch assistant blueprints for ChatGPT, Claude, Gemini, Grok, or portable Agent Skill format. Operates locally over stdio with read-only tools and no network, shell, account, or file-write access.
      3
      46 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Serves skill-defined JSON-in/JSON-out scripts as callable tools over MCP stdio, driven by a portable skill-runtime.json manifest that supplies each tool's title, description, and input schema. Exposes commands to validate, list, and run skills, so hosts can discover and invoke agent skills without custom per-skill glue code.
      8 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a distinct role: skill instructions, resource listing, reference reading, outline, excerpt, script retrieval, setup explanation, and workflow planning. The three reference-reading tools (get_blender_reference, get_blender_reference_outline, get_blender_reference_excerpt) operate on the same documents at different granularities, which could cause some misselection, but the descriptions clearly delineate low-context vs. bounded-window vs. full-read use cases.

    Naming Consistency5/5

    All tools follow a uniform snake_case verb_noun pattern scoped by the domain (get_blender_*, list_blender_*, plan_blender_workflow). No mixed conventions or abbreviation drift, making intent predictable from the name alone.

    Tool Count5/5

    Eight tools is well-scoped for a read-only skill/resource server with no redundancy. Every tool maps to a distinct access pattern (metadata, full read, outline, excerpt, script, setup, planning) and none feels padded.

    Completeness4/5

    The read-only resource surface is largely complete: discovery, granular reading, scripts, setup context, and planning are all covered. The main gap is a search/lookup tool to find which reference covers a topic without first listing files; otherwise no dead ends for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues