Tether
Related Servers
Alternatives to Tether
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.4122MIT
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect and modify live Blender scenes, manage objects and materials, render images, retrieve PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM backends.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scene objects and materials, render images, fetch PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM providers with runtime switching.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scenes, objects, materials, and renders, download PolyHaven assets, and switch between multiple LLM backends at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session with scene/object manipulation, rendering, PolyHaven asset tools, and runtime-switchable LLM provider backends.-
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes: open/close manage the session, run executes code, api_search looks up API, scene/view inspect, and asset_search/asset_import form a clean search-then-import pair. The only mild friction is the generic name 'status' (running apps) sitting beside 'generate_status' (generation job) and 'scene'/'view', which all report some kind of state; descriptions resolve it but the bare names could cause a first-glance misselection.
All names are lowercase snake_case, which is good, but they mix at least three conventions: verb_noun (asset_search, asset_import, generate_start, generate_status, api_search), bare verbs (open, close, run), and bare nouns (status, scene, view). The generate_* and asset_* prefixes give helpful grouping, but the overall set is not a single predictable pattern.
Eleven tools is well within the sweet spot for a rich Blender control server. Each tool occupies a distinct role (lifecycle, code execution, inspection, asset acquisition, AI generation) and none feels redundant or bolted on.
The surface covers session lifecycle (open/close/status), code execution and API discovery (run/api_search), visual and textual inspection (view/scene), asset search/import, and paid model generation with polling — a coherent end-to-end workflow. Minor gaps are that saving/exporting, undo, and closing a windowed Blender are not exposed as first-class tools (the latter is explicitly punted to run), though run provides a universal escape hatch.