No user-submitted related servers found.
Scored across 16 tools
Most tools have clearly distinct purposes: project read/save, page CRUD, asset saving, status/API setup, and image task lifecycle. The only potential confusion is between get_canvas_project and get_canvas_context, which both retrieve canvas data but differ in scope (full project vs. active page/selection).
All tool names follow a consistent verb_noun pattern in snake_case (get, save, create, rename, delete, start, open, prepare, submit, finalize, cleanup, list). The inclusion of 'modellix' and 'canvas' modifiers is logical and consistent throughout.
With 16 tools, the count is slightly above the typical 3-15 range, but each tool serves a distinct and necessary function in the canvas management and image task workflow. No tool feels redundant, so the count is well-justified.
The tool surface covers the full lifecycle: project read/write, page CRUD, asset management, status/API setup, and image task preparation, submission, status query, finalization, and cleanup. The only missing operation is project deletion, but that may be intentionally out of scope for a workspace-bound canvas.