Guide
Teams & Projects
Canvas
To find a character or product reference by name, pass
canvasId and nodeQuery
to canvas_content. It searches node titles across the canvas and returns up to
10 compact candidates in nodeLookup. In this mode, nodes and edges are
empty; they do not describe the full canvas. Use the returned nextOffset as
nodeOffset for more candidates, or read a candidate with nodeId to inspect its
current asset and version. Do not combine nodeQuery with nodeId or
includeAllVersions.
Nodes
Video audio control
Checkmodel_list for a video variant with supportsAudioToggle: true. With that model explicitly selected, set generateAudio: false on node_create, node_update, or each video in bulk_create_nodes to generate without audio. Set it to true to enable audio again.
The setting is saved on the node and reused by single and bulk runs. Omit it on updates to preserve the current setting. Auto model mode ignores saved audio overrides.
For a single generation, run_start also accepts a boolean generateAudio override. When running the saved node model, omit it to inherit the saved setting or model default. When overriding the model for a run, pass generateAudio explicitly. This controls new generations; it does not remove audio from an existing video. To mute source clips in a stitch while retaining narration overlays, use node_update.muteSourceAudio: true instead.
Groups
Edges
Runs
Node tools
Node tools post-process a node that already has a finished asset. They also work on file nodes that hold an uploaded image or video. Each returns a run ID — callrun_wait to block until it finishes, and the finished run activates the new version automatically.
Downloads
Models
Audio
Comments
Presence
The claim overlay names the agent working in that region. Pass
agentName to show_presence to set that name yourself; leave it out and the name of the client you connect through is used.
show_presence returns a presenceId. Pass it to every later show_presence and release_presence call for the same task, so the release clears your overlay even if your client opens a new connection for each tool call. release_presence returns removed: false when no overlay with that presenceId was showing.
An overlay you never release disappears on its own five minutes after your agent’s last request to Melius.
Presets
Files & imports
Team skills
Agent context
Display
Cast
Beta — this feature is rolling out gradually. Reach out to support if
you’d like access.
Clients that support MCP Apps show avatar choices and a video player with Download video. Other clients receive numbered choices and media links. Voice, background, prop and template pickers appear only when you explicitly request them.
Ask your agent to draft or edit the script in chat. Draft-only requests stop before generation. For generation requests, it infers settings from your brief. The default is Seedance 2.5, Auto voice, portrait 9:16, the model’s default resolution and no subtitles. You can request any supported model, aspect ratio, resolution, subtitles or specific voice in chat. Explicit settings take priority; incompatible choices need clarification. Technical settings are not shown as inline controls. Video style and speech delivery stay internal and do not appear as review fields. There is no tone control or history browser.
Scripts support both spoken lines with visual direction and separate silent action sections. Your agent can add gestures, demonstrations and reactions when they help your brief. For example, ask: “Explain how the Moon formed, act out the impact silently, then continue speaking.” Actions appear in the script review before generation and are not read aloud. You can also supply exact dialogue and stage directions in chat.
Naming an existing avatar in your first request already selects it. Your agent can prepare or generate using that name directly, without opening the library or asking you to confirm it. Matching ignores capitalization. If the name is missing or matches multiple avatars, the agent asks for clarification instead of substituting another avatar. After you confirm an avatar in a picker, your agent continues with that selection. If your client places the selection message in the chat box, press Send to continue. The agent can recover the named selection without opening another picker.
Generation uses your MCP client’s native tool approval. With auto-approve enabled in the client, a request such as “make 10 videos using Loopy” needs no additional Generate click for each video. Your agent reuses the named avatar, prepares all requested scripts and checks their combined estimate, then submits every video without waiting for earlier renders. Your plan and the generation queue determine how many render simultaneously. Multi-video requests use one batch review and one live batch card containing every video, completion/failure counts, downloads and View all in Cast. Each request supports up to 20 videos. Single videos retain their individual card. Existing credits and usage limits apply. Keep the conversation active until all requested videos are submitted. Accepted renders continue on the server; the agent cannot resume an unsubmitted batch after the client closes.
Saved avatars use a headshot cropped from the same identity image used by the Cast studio. No extra image generation is needed.
In Apps clients, the card opened by an accepted generation tracks that video through rendering and subtitles, then becomes the finished player. Your agent does not need another result call. Text-only clients poll accepted videos and return media links. Loading cards update automatically without an elapsed-time counter. Progress checks never restart generation. Each wait call uses a short window; an unfinished window continues checking the same video. A failed video stops waiting and shows its error. Requested subtitles finish before Download video retrieves the file. If subtitles still fail after retries, the original is available with a warning and the subtitle credits are refunded. You can ask the agent to check an existing run again without creating another video or card. If a status check fails, the card reports that the current status is unavailable and provides View in Cast. Batch cards check only unfinished videos and slow their retries during outages.
Your Cast review includes the selected prop image so you can verify it before generation. For an image already attached or present in your Cowork folder, the agent uses that file directly without searching Assets. If your team has access to Assets, you can select an existing image as a prop. Semantic library search requires Pro or above; uploading an image from chat does not. Otherwise, attach an image in your chat or skip the prop. Attachments require a client that can access and transfer the file; the remote MCP server cannot read your device’s files itself.
Cast follows the same MCP usage policy as the other tools. Ordinary Cast calls are recorded in your team’s MCP usage;
cast_result, cast_wait and cast_batch_result polling have the same counting exemption as other generation polling tools. Image and video generation use your team’s credits. Checking an existing run never restarts the video. For a video requested with subtitles, Melius adds them once the original video is ready, whether or not anything is checking. A subtitle pass that fails or stalls is retried, up to five passes in total, and checking never starts an extra one. If some candidates fail, the available images remain selectable with their original option numbers.
Sticky notes
Read sticky notes throughcanvas_content. The notes array includes each note’s ID, text, position, width, height, group and height mode. Use noteId for one note, or noteOffset: 0 followed by nextNoteOffset to page through notes. A grouped note’s position is relative to its group.
Use note_create to place a label and note_update to change its text or dimensions. Both require editor access. Omitted update fields are preserved. Set heightMode: "manual" to keep an exact height, or "auto" to fit the text.
noteId when updating it.