Back to rankings

Figma MCP: Run Weave Tools from External AI Agents

FigmaView original changelog

Figma extended its MCP server so Weave tools — the custom AI image workflows teams build inside Figma Weave — can now be triggered directly from external agent clients like ChatGPT, Claude, and Cursor, without opening Figma at all. An agent finds the right tool, runs it, tracks its progress, and returns the result inline in the conversation, while preserving context like prompts, images, and brand guidelines. Figma also launched a new MCP Catalog to help teams discover which agent clients are compatible. The update turns one-off Weave automations into reusable capabilities that live inside a team's existing AI toolchain.

Key Takeaways

  • Weave tools now run outside Figma entirely, callable directly from ChatGPT, Claude, or Cursor via Figma's MCP server, with no need to open the Weave interface.
  • Natural-language invocation is the interaction model: users simply ask their agent to run a named tool (e.g., "Run my Brand mockup tool"), and the agent finds, executes, and tracks it.
  • Context is preserved across the handoff, including the original prompt, supplied images, and brand guidelines, so results stay consistent with how the tool was built.
  • Figma published a new MCP Catalog (figma.com/mcp-catalog) to help teams identify which agent clients are already compatible with the Figma MCP server.
  • The release teases a further step: building new Weave workflows from inside an agent environment, without opening Figma at all, signaling more agent-native tooling to come.
  • This extends Figma's broader 2026 strategy of opening the Model Context Protocol (MCP) surface beyond design files (Dev Mode, Make, Slides) to now include Weave's AI image workflows.

Weave Tools Go Wherever the Agent Goes

Figma has extended its MCP server so that Weave tools — the custom AI image workflows designers and teams build inside Figma Weave, like background swaps, logo placement, or aspect-ratio changes — can now be executed from outside Figma entirely. Any MCP-compatible agent client, including ChatGPT, Claude, and Cursor, can locate a Weave tool, run it, and return the result directly inside the conversation.

Previously, running a Weave tool meant opening Figma and working inside the Weave interface. With this update, a team's custom tools become callable capabilities that any connected agent can invoke on demand, without a context switch.

How It Works

The workflow follows a simple pattern: a user asks their agent, in natural language, to run a specific Weave tool against a set of inputs. For example, a team that has built a "Brand mockup" tool that turns product photos into on-brand mockups can simply tell an agent, "Run my Brand mockup tool in Figma Weave with these images." The agent identifies the matching tool, executes it, tracks its progress, and surfaces the finished result back in the chat.

Critically, the agent retains the surrounding context throughout the exchange, including the original prompt, any images supplied, and relevant brand guidelines, so the output stays consistent with how the tool was designed to be used inside Figma.

A New MCP Catalog

Alongside the release, Figma published an MCP Catalog, a directory that helps teams see which agent clients are compatible with Figma's MCP server and how to connect them. This makes it easier for teams already standardized on a particular AI coding agent or assistant to wire up Weave tool access without trial and error.

Why It Matters

This update pushes Figma Weave further into the broader "agentic" workflow that Figma has been building toward across 2026: rather than keeping AI-powered design tooling siloed inside the Figma app, custom tools now travel with whatever agent a team already uses for day-to-day work. For design and marketing teams that lean on repeatable Weave automations, this removes a step from the loop and keeps tool use closer to where planning and content work already happens.

Figma's release notes also teased a follow-up capability: building new Weave workflows from directly inside an agent environment, without ever opening Figma, suggesting this is the first step in a broader push to make Weave tool creation, not just execution, agent-native.