Skip to main content
Glama

Related Servers

Alternatives to FaceLink

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to drive Blender 5.2 LTS through natural language, with tools for scene inspection, object creation and transformation, material and modifier handling, rendering, viewport capture, and guarded Python execution.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language creation and refinement of Blender scenes through structured MCP tools, with persistent object identity, visual validation, and reversible edits.
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.
      71
      44
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language control of Blender through the Model Context Protocol, supporting scene/file inspection, object management, primitive creation, transforms, and provider capabilities for the CDT engineering workflow.
      MIT

    TDQS

    B3.2/5.0

    Scored across 17 tools

    Disambiguation4/5

    The tools are largely separated by lifecycle stage and resource type, such as validate, preview, stage, apply, and rollback. A couple of pairs, like validate_retarget_profile vs analyze_retarget_profile and apply_staged_patch vs apply_scene_patch, are close enough to require careful reading, but the descriptions do distinguish them.

    Naming Consistency4/5

    Most tools follow a clean action_object snake_case pattern like list_, get_, validate_, stage_, apply_, and discard_. facelink_health breaks the pattern as a noun phrase, and rollback_to_revision uses a preposition instead of a direct object, but these are minor deviations.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 range, but the server covers several distinct workflow areas: instance health, retargeting, shots, staged patches, and revisions. The count is reasonable for the scope, though it could be tightened.

    Completeness4/5

    The set covers the core safety-oriented lifecycle: scan, validate, preview, stage, review, apply, and rollback. Obvious minor gaps exist, such as no Blender job submission/cancellation and no explicit apply/save for retarget profiles, but agents can work around them via scene patches and external job submission.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues