A
licenseA
qualityB
maintenanceEnables AI assistants to control Blender via MCP tools for scene manipulation, material assignment, rendering, and Python script execution.
2
27
121 PyPI
33
MIT
reels
by Endroe
Related Servers
Alternatives to reels
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build models, import assets, animate scenes, render images, and save versioned projects through validated MCP tools backed by headless Blender, with a live browser viewer for inspection.GPL 3.0
- AlicenseAqualityCmaintenanceEnables AI assistants to control a Blender instance through MCP tools, supporting scene creation, editing, and asset exchange via HTTP and background CLI processes.26Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables local Blender-based product modeling and photography by exposing project management, scene editing, rendering, image inspection, and asset publishing tools to MCP hosts like Claude Code, with versioned .blend revisions and PNG renders.GPL 3.0
- FlicenseNot gradedqualityDmaintenanceEnables natural language control of Blender 3D through local AI models, allowing MCP clients to create, modify, and render scenes, apply materials, and execute Python code in Blender.-
- AlicenseNot gradedqualityBmaintenanceEnables creating and editing 9:16 video reels programmatically through MCP tool calls, with ffmpeg rendering, caption styling, and optional project presets.1MIT
TDQS
B3.3/5.0
Scored across 21 tools
Disambiguation4/5
Most tools have clearly distinct roles: project listing/creation, asset search/registration/review/resolution, shot/entity edits, timeline, audio and render are separable. The weakest boundaries are reels_list vs reels_get (project vs shot/document read), and the dense asset family (search_assets, search_remote_assets, get_asset, preview_asset, resolve_asset, register_asset, download_asset), where descriptions do the heavy lifting but an agent could still misselect a first step.
Naming Consistency4/5
All tools share a predictable reels_ prefix and snake_case verb_noun form. The deviation is that project-scoped tools drop the noun (reels_list, reels_create, reels_get, reels_preview, reels_render) while asset tools name their resource explicitly, so reels_get/reels_list read less self-explanatory than reels_get_asset.
Tool Count3/5
At 21 tools the surface is on the heavy side for a single MCP server, and the asset bank alone consumes eight tools (search, search_remote, get, preview, register, review, resolve, download). Each has a defensible role, but several are fine-grained steps that could reasonably be consolidated.
Completeness4/5
The lifecycle is largely covered: project creation/read, shot and entity patching, timeline mutation, audio attachment, preview/render with status, plus local and remote asset import, registration, review and resolution. Gaps remain around destructive/administrative operations — no project delete or metadata update, no render cancel/listing, and no entity or asset removal.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues