Figma MCP | Weave Tools Run Directly From AI Agents
Figma is connecting Weave workflows directly with AI agents through the Figma MCP server. Released on August 11, 2026, the update lets users run published Figma Weave tools from supported clients such as ChatGPT, Claude, and Cursor, allowing prompts, images, brand guidelines, and generated results to remain inside the same conversational workflow instead of requiring constant switching between apps.
Figma brings reusable Weave workflows into AI conversations
Figma Weave tools are published workflows that can package repeatable creative processes into something an agent can run when needed. With the new MCP integration, users no longer need to manually open Weave each time they want to execute one of those tools. They can describe the task conversationally and let the connected agent identify the appropriate workflow.
The agent can find an available Weave tool, inspect the inputs it requires, send the necessary information, start the run, track its progress, and return the generated output when processing is complete. This makes Weave tools behave more like reusable creative capabilities inside a broader AI workspace rather than isolated workflows that always require their own interface.
Prompts, images, and brand context can stay with the agent
One of the most useful parts of the integration is context continuity. A conversation may already contain prompts, reference images, instructions, or brand guidelines needed for a creative task. Instead of transferring that context into another application manually, the agent can use it while preparing the inputs for the selected Weave workflow.
Figma gives the example of a custom Brand mockup tool that converts product images into finished mockups. A user can ask the agent to run that specific Weave tool with attached images, and the workflow can proceed from the conversation through execution and back to the returned result.
MCP exposes dedicated controls for running Weave tools
The Figma MCP server includes dedicated operations for discovering available Weave tools, checking their required inputs, uploading supported assets, starting runs, retrieving results, and canceling jobs that are still processing. This gives compatible agents a structured way to work with the underlying workflow rather than relying on improvised instructions.
Asset inputs can include common image, video, audio, and 3D formats, depending on what the individual Weave tool expects. For designers, this means a custom workflow could potentially receive the same visual material already being discussed with an agent and return an output without breaking the surrounding design conversation.
Weave credits and account requirements remain separate
Running a Weave tool through Figma MCP uses Weave credits rather than Figma AI credits. When a run has a cost, the connected agent can show the required amount and request confirmation before execution. Free runs do not require that additional confirmation step.
Figma's developer documentation also specifies that running Weave tools through MCP requires a paid standalone Figma Weave account. Availability therefore depends not only on having a compatible MCP client, but also on the user's Weave setup and the published tools available in the active workspace.
IMPORTANT: Running Figma Weave tools through MCP requires a paid standalone Figma Weave account and uses Weave credits, not Figma AI credits. Paid runs require cost confirmation before execution.{alertWarning}
Daisuki's Take: What This Means for Web Designers
The interesting part of this update is not simply that another creative tool supports MCP. Figma is making reusable visual workflows callable from the same agents designers may already use for research, frontend work, content preparation, or broader project coordination.
For web designers, that could make specialized asset workflows easier to reuse. A team could prepare branded imagery, mockups, or other visual material through a predefined Weave tool while keeping the website brief, references, and surrounding conversation available to the agent coordinating the task.
We see the strongest value in repeatable workflows rather than one-off generation. When a team has already built a reliable Weave tool around its brand or production rules, MCP gives that workflow another entry point and reduces the friction between discussing a design task and actually running the creative process behind it.
Sources and Recommended Links
- Figma MCP: Run Weave tools, right from your favorite agent | Figma Official Release Notes
- Tools and prompts | Figma Official Developer Documentation
