Joey Banks shares a free lesson from his course with Dive readers on how to use Figma’s MCP Server. 

In this replay from the June 4th, 2025 webinar, learn more about the latest tools that help you express more in your Figma designs. Lauren Budorick, Rogie King, and Tim Van Damme will walk through improvements to vector editing, as well as new brushes, fills, and effects.

Rogie walks through quality of life updates for Figma Draw’s variable width stroke feature. Now you can select a width point and double click to enter a numerical value; after selecting a width point, you can go to the next one with Tab and the previous one with Shift-Tab shortcuts; with a custom width profile, you can see a preview of the shape or edit the width profile from the menu; hold Control to disable Snap to Pixel for more precision; select two width points by holding Shift and resize both together. 

Rogie King introduces a new brush type in Figma Draw — scatter brushes. Make sure to read a fun behind-the-scenes look at how Rogie and Molly worked together to create and name the new brushes.

Miggi shows a new Figma Draw feature. You can now take any flattened vector path and offset it to expand or retract it.

Jack Michalak and Tammy Taabassum pair with Supabase​’s Chris Caruso to demo Make’s new Supabase connector, wiring auth, file uploads, and live Postgres tables straight from a Figma frame. Nice primer on turning a design into a data-backed web app with almost no code.

Figma Sites now supports apex (top-level, like exam​ple​.com) domains and custom subdomains (like yourname.figma.site) so that you have more options for personalizing your URL.

This is a pretty nice QoL improvement. Want to see it in Figma Design too!

Designer Advocate Lauren breaks down how to create code layers in Figma Sites.

Software engineers Darragh Burke and Alex Kern share the story behind the creation of code layers to bring design and code together. ​“Building code layers in Figma required us to reconcile two different models of thinking about software: design and code. Today, Figma’s visual canvas is an open-ended, flexible environment that enables users to rapidly iterate on designs. Code unlocks further capabilities, but it’s more structured — it requires hierarchical organization and precise syntax. To reconcile these two models, we needed to create a hybrid approach that honored the rapid, exploratory nature of design while unlocking the full capabilities of code.”

Now you can bring an existing design library to Figma Make, so the model can extract color palette and usage guidelines, typography and custom fonts, as well as core styling elements. You can also manually define rules for the model to follow via a guide​line​.md file. Watch the above video from Make PM Holly Li, or read the help article.

You can now adjust the width of your stroke at any given point along a path with the new variable width stroke vector editing tool. Variable width stroke also makes it possible for users to draw with pressure sensitivity on tablets. Figma will set the stroke width to reflect the amount of pressure applied at each point when drawing with a stylus, which makes freehand drawing in Figma more realistic. (Still no iPad app though.)

Jamayal makes cool atmospheric illustrations in Figma Draw.

Developer Advocate Akbar Mirza and Product Manager Yarden Katz provide a live update on Figma’s Dev Mode MCP (Model Context Protocol) server, explaining what MCP is, how it works, how to set it up, and how it helps bridge the gap between design and code. They also cover the new support for Annotations, which allows designers to add accessibility, behavior, and content information to their design files, which the AI agent can then use to generate more accurate code. Finally, they discuss the importance of aligning variable names between design and code. Don’t miss the follow-up video where Akbar and Yarden answer viewer questions from the livestream. 

“New in Dev Mode MCP Server: Annotations are included as design context. Generated code now benefits from both the structure of your design and your design intent.”

Developer Advocate Jake Albaugh shows how to bring design context from Figma directly to your agentic coding tools with the new Dev Mode MCP server.

Great demo of code layers by Niko, who is now a product manager for interactivity. ​“Code now belongs; make a mess, rev, refine.”

Nolan Perkins argues that code layers are ​“a window into what our design workflows will look like in the age of AI.”

“We built code layers—interactive elements backed by custom React code—in Figma Sites to help you experiment with interaction and motion without additional technical knowledge or outside help. Whether you’re creating an element from scratch or riffing on an existing design, code layers allow you to add dynamic functionality to your site—from flyouts and dropdowns to shaders and maps—by converting components to code layers, chatting with AI to build and tweak them, or editing directly in Figma’s code composer. And, you can generate multiple code layer variations to compare your ideas side-by-side and experiment freely—all in the Figma canvas.”

Figma acquired Payload, an open-source Next.js CMS. James Mikrut, founder of Payload: ​“Figma and Payload together can and will solve a problem that’s been bugging me (and probably all of you) for years. The gap between design and code still exists. Designers create in Figma, then devs recreate in code, then content teams struggle to maintain it all. It’s inefficient and frustrating. And historically, the CMS tends to make it worse. With Figma, we can (and will) solve these problems in new ways without compromising.”