Skip to main content
Glama
tfmstyle-blender-tools

tfmstyle-blender-tools

by TFMSTYLE

Related Servers

Alternatives to tfmstyle-blender-tools

No user-submitted related servers found.

    Related Servers

    • 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
    • F
      license
      A
      quality
      B
      maintenance
      Enables an AI assistant to operate a running Blender instance through 428 typed, parameter-checking tools for modeling, materials, UVs, rigging, animation, physics, geometry nodes, and rendering, while reading results back.
      3
      3
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session, inspect and modify scenes, manage PolyHaven assets, render images, and route prompts through configurable local or OpenAI-compatible LLM backends.
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: list_addons enumerates addons, describe_addon inspects one addon's actions/settings, and run_addon applies settings or executes actions. There is no meaningful overlap in purpose, and the descriptions make the boundaries clear.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern: list_addons, describe_addon, run_addon. The naming is predictable and easy to map to the intended operations.

    Tool Count5/5

    Three tools are well-scoped for a server focused on managing TFMSTYLE Blender addons: one to enumerate, one to inspect, and one to act. Each tool earns its place without redundancy.

    Completeness4/5

    The surface covers the core lifecycle of discovering addons, inspecting their settings/actions, and running them with validation and confirmation. Minor gaps exist, such as enabling/disabling addons or viewing logs, but core workflows are covered.