Use this file to discover all available pages before exploring further.
These are the tools exposed by the VibeFlow MCP server that touch the canvas product. They’re available to any MCP-compatible client connected via the MCP overview.The broader VibeFlow MCP also exposes UI-project and design-system tools (initiate_project, deploy_project, create_design_system, etc.). Those are documented separately at docs.vibeflow.ai.
Patches one or more elements inside a frame using stable element selectors. Prefer this over write_canvas_frame when you only need surgical edits. Equivalent to the canvas agent’s update_element tool.
Arg
Required
Description
canvasId
Yes
The canvas id.
frameId
Yes
The frame id.
patches
Yes
An array of patches. Each one is { selector, html }, { selector, text }, or { selector, style }.
Runs the full canvas agent with the same tool surface, brand contract, and credit gating as the in-app chat. The agent decides which canvas tools to call based on your brief.
Arg
Required
Description
canvasId
Yes
The canvas to run against.
message
Yes
The brief. Plain text.
attachments
No
Array of image URLs or asset ids.
referenceFrameIds
No
Frames the agent should read before planning.
Returns a streamed series of events (frame creates, element updates, narration), then a final { creditsUsed, summary }.
This is the most powerful tool in the set. For multi-step jobs (“clone this site, then build a 5-frame deck against the new system”) prefer run_canvas_agent over chaining low-level tools by hand.