opentoonz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENTOONZ_ROOT | No | OpenToonz runtime root; the server seeds isolated SystemVar.ini and passes it as TOONZROOT | workspace root |
| OPENTOONZ_BUILD_DIR | No | Directory containing bin/tcomposer and bin/tconverter | $WORKSPACE/toonz/build |
| OPENTOONZ_TCOMPOSER | No | Explicit tcomposer path | |
| OPENTOONZ_WORKSPACE | No | Root directory that all paths must remain inside | current directory, or sibling ../opentoonz |
| OPENTOONZ_TCONVERTER | No | Explicit tconverter path | |
| OPENTOONZ_ARTIFACT_DIR | No | Default output directory for generated artifacts | .mcp-artifacts inside workspace |
| OPENTOONZ_LIBRARY_PATH | No | Optional native library path for build-tree binaries | $BUILD_DIR/lib/opentoonz when present |
| OPENTOONZ_RUNTIME_HOME | No | Isolated HOME, XDG config, and cache root for native subprocesses | .mcp-artifacts/.runtime inside workspace |
| OPENTOONZ_MCP_TIMEOUT_MS | No | Default subprocess timeout | 120000 |
| OPENTOONZ_MCP_MAX_OUTPUT_BYTES | No | Captured stdout/stderr limit per subprocess | 2000000 |
| OPENTOONZ_MCP_MAX_SCAN_ENTRIES | No | Filesystem discovery limit | 10000 |
| OPENTOONZ_MCP_MAX_METADATA_BYTES | No | Maximum project, scene, and scenes.xml metadata file size | 32000000 |
| OPENTOONZ_MCP_MAX_INSPECT_CONCURRENCY | No | Maximum concurrent metadata inspections | 4 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_manifestB | Return a live manifest of the configured workspace, discovered projects/scenes/levels, runtime paths, and available OpenToonz command-line capabilities. |
| list_projectsB | Discover OpenToonz project descriptors inside the workspace. Results are read-only and include project folders and parser warnings. |
| inspect_projectA | Parse one OpenToonz project descriptor and report its version, logical folder aliases, resolved in-workspace paths, and warnings. |
| list_scenesC | Discover .tnz and legacy .tab scenes. Optionally scope results to a project directory or descriptor. |
| inspect_sceneA | Read scene header metadata and extract serialized level/scanned-path references without loading or mutating scene resources. |
| validate_scene_resourcesA | Resolve scene path aliases and report missing or workspace-external level and scanned-image references. This is read-only. |
| list_level_filesB | List recognized OpenToonz drawing, vector, raster, palette-adjacent, and image level files under an optional workspace-relative directory. |
| list_artifactsA | List files produced by MCP render and conversion operations in the configured artifact directory. |
| render_previewB | Render one scene frame with tcomposer into a new .mcp-artifacts file. Existing files are never overwritten. Requires a built tcomposer executable. |
| render_sceneB | Render an image sequence or output file with tcomposer. The destination must be new and inside the configured workspace; no arbitrary shell commands are exposed. |
| convert_levelC | Convert a level with tconverter into a new destination. Existing files are refused to avoid interactive overwrite prompts and accidental data loss. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review-scene-health | Prepare a focused prompt for checking scene metadata and missing resources. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workspace-manifest | Live JSON manifest for the configured OpenToonz workspace. |
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.