You open Figma to make one brand mockup, pick some images in Weave, paste the result into ChatGPT, and repeat. Now they're saying you can do the whole thing in one chat message. But there's a hidden invoice attached to that convenience.
Everyone's like "one fewer app, nice"
August 11, 2026. Figma dropped this on their release notes: "You can now execute Figma Weave tools directly from clients like ChatGPT, Claude, and Cursor." The agent listens to what you need, finds the right tool, runs it, and hands back results in the chat window.
Their example was concrete. Say you've built a Brand mockup tool in Weave that transforms product shots into mockups. You just tell the agent "run the Brand mockup tool on these images," and it handles everything — finding the tool, executing it, tracking progress, and pulling results back.
This works because of Figma's MCP catalog. Claude supports the full product suite (Figma Design, Make, FigJam, Slides, Weave), and so do ChatGPT and Cursor. Since it's Model Context Protocol, you can wire it to a remote server or go local.
But the real thing that shrank wasn't tabs — it was context amnesia
Here's where it's easy to miss the point: "you save an app switch" isn't actually the pitch. Look at Figma's own framing and the emphasis lands elsewhere. "Execute Weave tools without switching apps, keeping context — prompts, images, brand guidelines — intact the whole time." What actually disappeared isn't the number of apps; it's the context loss you'd take every time you jumped between them.
Why context matters becomes obvious when you look at what Weave workflows actually do. Figma shared five representative workflows from the community, and they include things like analyzing two reference images to extract style guides, then morphing those styles across different aspect ratios (1:1, desktop, 9:16), and even converting static images into fully rotatable 3D models. This stuff breaks the moment your style, tone, or brand rules get dropped — you'd have to re-explain everything from scratch.
Real practitioners have felt this friction. A developer who chained a vectorization tool with Figma MCP to convert images to SVG and snap them to design system grids described the whole pipeline completing "in seconds." Because it auto-reads component libraries and spacing tokens, the output isn't generic placeholder — it's actual design system spec for that team.
But nobody ran the numbers on the bill
Problem is, convenience isn't free. One UX/UI designer in Korea posted skepticism on Threads: LLM subscriptions run $20–200/month, and now you're layering Figma on top. You need both subscriptions running to make this work — the post picked up 43 likes and 22 replies.
The per-plan limits drive the point home. Starter caps MCP tool calls at 6 per month. Canvas writes (write permissions) are Dev/Full only — technically free during beta, but realistic to expect that to flip once beta ends.
| Old Way | Figma MCP + Weave | |
|---|---|---|
| Where tools run | Inside Figma only | ChatGPT·Claude·Cursor, anywhere |
| Context stays put | Re-explain each app switch | Prompts·images·guidelines auto-kept |
| Monthly cost | Figma subscription | Figma + LLM dual subscription |
| Canvas writes | No limits | Dev/Full tier only (free during beta) |
So here's how to try it today
- First, check if you have tools built in Weave
What MCP calls are workflows you've already set up. If nothing's there yet, go build something node-based in Weave first — things like style transfer or mockup generation. - Pick your client in the MCP catalog
Choose ChatGPT, Claude, or Cursor, follow the setup for connecting to the remote server (mcp.figma.com), and you're wired. - Know your permission tier
Read access works on all plans, but canvas writes and Weave tool execution depend on your tier. Starter limits you to 6 calls/month — keep that in mind. - Use the exact tool name in your prompt
Tell the agent "run Brand mockup on these 3 images" using the exact name you gave your Weave tool, and it'll find and execute it. - Treat chat output as draft, refine in Figma
What lands in the chat window is a starting point, not the final version. Flip back to Figma Weave to dial in the details.
Dig deeper
Figma MCP Catalog Official reference covering 18+ clients, product support per tier, and permission scope figma.com
Connecting Figma and Weave Official post on invoking Weave tools from within Figma Design and remotely via MCP figma.com
Five Figma Weave Workflows Five real-world Weave workflows spanning style definition through 3D transformation and video rendering figma.com
Guide to the Figma MCP server Official help center docs covering Remote vs. Desktop, per-plan call limits, and read/write permission matrix help.figma.com
figma/mcp-server-guide Official GitHub repo with the full MCP tool reference (get_design_context, get_variable_defs, etc.) and technical specs github.com
Figma Weave + MCP Server Pipeline Tutorial Hands-on walkthrough: vectorize images to SVG and auto-snap them to your design system grid vectosolve.com
