tfmstyle-blender-tools
Related Servers
Alternatives to tfmstyle-blender-tools
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceBuild Blender scenes through 4 tools and 338 tokens of fixed context: on-demand operation schemas, batches of up to 100 edits, preview captures and permission-gated Python for full bpy access.418MIT
- AlicenseBqualityBmaintenanceEnables 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.28GPL 3.0
- FlicenseAqualityBmaintenanceEnables 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.33-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create and manipulate 3D scenes, objects, and materials, execute Blender Python, capture visual verification views, and generate or import assets and models.MIT
- 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 control a live Blender session, including scene and object operations, materials, rendering, PolyHaven asset downloads, and prompts to configurable LLM backends through MCP tools.-
TDQS
Scored across 3 tools
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.
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.
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.
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.