External agents can help with flare.design projects when you want another tool to inspect the canvas, draft changes, generate media, or automate focused edits. The goal is not to hand the whole project away. The best workflow keeps humans in control of direction and lets agents handle bounded tasks.
Use this page for the product workflow. Use Configure the flare.design MCP server when you need endpoints, scopes, and tool names.
Good agent tasks
Agents work best when the task has visible context and a clear stopping point.
| Task | Good request |
|---|---|
| Canvas review | ”Look at the selected frame and suggest three hierarchy fixes.” |
| Copy variants | ”Create five shorter headline options for this frame and place them to the right.” |
| Media revision | ”Read the annotations on this image and generate a revised version beside the original.” |
| Layout expansion | ”Make two 9:16 variants from this 1:1 frame, keeping the product readable.” |
| Motion planning | ”Apply a subtle motion plan to this frame; avoid animating every layer.” |
| Project summary | ”List the final frame, media assets, and export checklist for this project.” |
Avoid broad requests like “make this better” unless you also say what should stay fixed: format, brand, audience, duration, text, or existing assets.
Start from canvas context
The canvas is the shared reference point. Before asking an agent to write, select the frame, layer, image, or group that matters.
Useful context includes:
- The active frame or selected layer.
- Nearby references outside the export frame.
- Image annotations, arrows, crop notes, or text comments.
- Asset names, generation prompts, and source model metadata.
- The intended output format, such as 9:16 MP4 or 1:1 still.
- Any constraint that should not change, such as brand color, product crop, duration, or approved copy.
When the agent can read live canvas context, it can place new material near your selection instead of dropping it at a random coordinate.
Keep permissions intentional
MCP authorization separates project, canvas, asset, generation, and render capabilities. Grant the minimum access that matches the task.
| Need | Permissions |
|---|---|
| Summarize or audit a project | projects:read, canvas:read |
| Place existing assets or generated files | projects:read, canvas:read, canvas:write, assets:read, assets:write |
| Edit text, layout, order, or motion | projects:read, canvas:read, canvas:write |
| Start Flare backend generation jobs | Add generation:create |
| Start cloud render jobs | Add render:create |
Write access lets the client change the canvas. Generation and render creation can consume Flares, render allowance, or plan usage, so keep those scopes off unless the task needs them.
Review before accepting
Treat agent output as a proposal. Keep the original frame nearby and compare before replacing anything.
A clean review loop:
- Duplicate the frame or ask the agent to place variants beside the original.
- Check text readability, crop, timing, and brand fit.
- Keep the best candidate and move rejected versions away from the final export frame.
- Rename useful generated assets so they are searchable later.
- Export a short review pass only after the frame reads clearly.
If an edit changes more than expected, use undo or reload the previous saved project state before continuing.
Generated media
When an agent creates an image or edit outside flare.design, it should upload the actual file bytes and then place the asset on the canvas. Avoid putting base64, data URLs, or local file paths into MCP JSON.
Recommended flow:
- The agent generates or edits a local image file.
- It uploads the file through a short-lived binary upload session.
- It places the returned asset beside the selected frame or target image.
- You compare the new asset with the original before replacing anything.
This keeps generated media in the asset library with source metadata instead of turning it into an anonymous canvas-only image.
Better prompts
Give the agent a small role, a target, and a boundary:
- “Use the selected 9:16 frame. Make three alternate opening title treatments. Do not change the product image.”
- “Use the image annotations only. Generate one revised image, upload it, and place it to the right of the original.”
- “Read the selected frame and apply motion under 4 seconds. Keep the logo visible at the end.”
- “Summarize the project and tell me which assets look unused. Do not delete anything.”
Short, concrete prompts beat long vague briefs. Add constraints when something matters more than novelty.
When to switch to setup docs
Read Configure the flare.design MCP server when you need to connect a client, choose scopes, understand tool families, upload generated media, or run a smoke test.