opentoonz-mcp
Related Servers
Alternatives to opentoonz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents to drive OpenToonz headlessly through MCP tools for creating workspaces and scenes, drawing or importing frames as levels, placing cells on the xsheet, and rendering frames, PNG sequences, or MP4 videos. Also exposes a generic script escape hatch for the rest of the OpenToonz JS API.231MIT
- AlicenseAqualityCmaintenanceEnables CLI-first Aseprite automation with staging workspaces, supporting sprite inspection, patching, export, preview, and atomic file commits via file_commit.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to plan, capture, beat-analyze, render, verify and visually inspect deterministic beat-synced trailers and scene programs inside a workspace, including stills, contact sheets, timeline linting, editor interchange exports and authored audio arrangements. It also produces typed on-chain scene bundles with local-only reuse review and browser/offline playback checks.MIT
- FlicenseBqualityBmaintenanceEnables safe, observable Blender research by exposing structured tools for viewport capture, object and material edits, semantic scene creation, and managed .blend project lifecycles with transactional rollback and validation.42-
- AlicenseNot gradedqualityCmaintenanceEnables clients to create, query and edit QGIS projects and vector data in an isolated, new headless PyQGIS process, exporting GeoJSON/GeoPackage, saving and reopening editable QGZ bundles, and rendering PNG maps through typed MCP tools. All operations are workspace-relative with strict path and geometry validation, and never attach to or modify a running QGIS desktop session.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.19MIT
TDQS
Scored across 11 tools
Most tools target clearly distinct resources or actions: listing projects, scenes, levels, and artifacts is separate from inspecting and validating them. The main potential confusion is between render_preview and render_scene, and somewhat between workspace_manifest and the various list/inspect tools, though the descriptions clarify the intended boundaries.
The set is mostly consistent snake_case with verb_noun patterns such as list_projects, inspect_scene, render_scene, and convert_level. The notable deviation is workspace_manifest, which is noun-based rather than following the verb_noun convention.
Eleven tools is well within a reasonable range and each tool appears to earn its place by covering discovery, inspection, validation, rendering, conversion, or artifact listing. The surface is broad enough for the OpenToonz workflow without feeling excessive.
The server covers the core inspection and production lifecycle: discovering projects/scenes/levels, inspecting metadata, validating resources, rendering previews and sequences, converting levels, and listing artifacts. Minor gaps remain, such as direct inspection of individual level files or artifact management beyond listing, but agents can work around these.