Figma MCP: Run Weave Video and Image Models from External AI Agents
FigmaFigma now lets external AI agents run the video and image models from Figma Weave, such as Seedance, Kling and Nano Banana, through the Figma MCP server. Users can generate media from MCP-compatible agents without opening Weave. Generations consume Weave credits.
Key Takeaways
- Weave's video and image models are now callable from external agents, with Seedance, Kling and Nano Banana named as examples in the release notes.
- The update goes beyond the August release, which exposed only user-built Weave tools to agents such as Claude, ChatGPT and Cursor.
- Generations consume Weave credits, so usage is metered inside Figma's own billing rather than by the agent client.
- Users can generate media without opening Weave, which keeps designers inside the agent chat they already work in.
- The Figma MCP server is positioned as the single connection point for both design context and generative media.
- Figma's documentation for the earlier release says agents confirm before paid runs and that Weave workflow creation and editing is not available through MCP.
Weave models, now reachable from any MCP agent
Figma extended its MCP server so that agents outside Figma can call the generative video and image models available in Figma Weave. The release notes name Seedance, Kling and Nano Banana as examples. Until now, external agents could run only Weave tools, the reusable workflows that users build in Weave. They can now reach the underlying models too.
Builds on the August Weave tools update
On August 11, 2026, Figma made Weave tools callable from clients such as Claude, ChatGPT and Cursor through the Figma MCP server. The October 26 update widens that connection from finished tools to the models themselves. A designer working in an agent chat can ask for an image or a short video clip. The agent can then run the matching Weave model and return the result in the conversation. The user does not need to build a workflow first or switch to the Weave canvas.
Credits and cost
Generations run through this path consume Weave credits, the same currency used inside Weave. Figma's help documentation for the earlier Weave MCP release states that agents ask for confirmation before any paid run. The release notes for this update only state that credits are consumed. The documentation for the earlier release says creating and editing Weave workflows through MCP is not supported.
Why it matters
Generative video and image models are increasingly used from inside coding and chat agents. By exposing Weave's model lineup through MCP, Figma places Weave as a media-generation backend for those agents. Teams that already use Figma MCP for design context can add image and video generation to the same agent workflow. Figma also ties the generations to Weave's credit system rather than to the agent provider.