FaceLink
Related Servers
Alternatives to FaceLink
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to drive a live Blender session over MCP by inspecting scenes, creating and modifying objects, assigning materials, rendering images, and fetching PolyHaven assets. It also exposes prompt-based scene building and review workflows backed by a provider-agnostic LLM layer (Ollama, LM Studio, llama.cpp, OpenAI-compatible endpoints, Azure) that can be switched at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, including scene and object operations, rendering, and PolyHaven asset workflows. Supports provider-agnostic LLM backends that can be switched at runtime through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, including scene and object operations, materials, rendering, PolyHaven asset downloads, and prompts to configurable LLM backends through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session through MCP tools for scene/object manipulation, rendering, PolyHaven asset access, and guided scene-building prompts. It supports provider-agnostic LLM backends that can be configured or switched at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session through MCP tools for scene and object manipulation, rendering, PolyHaven asset search/download/texturing, and guided scene workflows, while allowing runtime switching between local or OpenAI-compatible LLM providers.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a live Blender session over MCP — inspecting scenes, creating and modifying objects, applying materials, rendering, and pulling PolyHaven assets — while routing natural-language prompts through a provider-agnostic LLM backend (Ollama, LM Studio, llama.cpp, OpenAI-compatible endpoints, or Azure) that can be switched at runtime.-
TDQS
Scored across 17 tools
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.
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.
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.
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.