Modellix Agent Canvas
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_canvas_projectA | Read the workspace-local Canvas project, pages, Excalidraw elements, business metadata, and optionally hydrated image data. |
| save_canvas_projectA | Atomically save a validated Canvas project inside the bound workspace. Image data is externalized into content-addressed local assets. |
| get_canvas_contextA | Return the active page and selected Canvas business objects without returning image bytes or secrets. |
| create_canvas_pageB | Create and activate a new workspace-local Canvas page. |
| rename_canvas_pageB | Rename an existing Canvas page. |
| delete_canvas_pageA | Delete a Canvas page while preserving the rule that every project has at least one page. |
| save_canvas_assetA | Save a bounded bitmap or sanitized SVG as a content-addressed project asset for later Canvas or image-task use. |
| get_modellix_canvas_statusB | Check workspace binding, CLI dependency compatibility, persistent API-key status, approved models, and Canvas mode without exposing secrets. |
| start_modellix_api_key_setupA | Create a short-lived loopback form that validates and stores a Modellix API key through the installed CLI dependency. Create a production key at https://www.modellix.ai/console/api-key. The key is never a tool argument. |
| open_modellix_canvasA | Open the workspace-bound Canvas. MCP Apps hosts receive the embedded app; other compatible MCP hosts receive a short-lived loopback URL. |
| prepare_modellix_image_taskA | Resolve ordered project assets, select an approved model, disclose effective output and estimated cost, and return a short-lived confirmation fingerprint. Does not upload or submit. |
| submit_modellix_image_taskA | After explicit confirmation, revalidate the route, upload ordered inputs, and create one paid Modellix task per requested output. |
| get_modellix_image_taskA | Query one task recorded in this workspace and return normalized status without exposing temporary result URLs. |
| finalize_modellix_image_taskA | Download a successful task into controlled staging, insert or replace Canvas objects, persist project assets, and clean temporary uploads. |
| cleanup_modellix_canvas_uploadsA | Retry deletion of temporary File API inputs retained after terminal image tasks. |
| list_modellix_canvas_tasksB | List redacted workspace-local operation summaries for recovery. Prompts, secrets, absolute paths, and temporary URLs are omitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| modellix-agent-canvas-app | Workspace-local infinite canvas for visual ideation, AI image workflows, HTML drafts, and presentations. |
TDQS
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.