Figma updates MCP server with Slides, FigJam, Make, and image exports

• Figma expanded its MCP server beyond design-file edits: figma's update post says it can now generate and edit decks in Figma Slides, build FigJam boards from data, and roundtrip code into Figma Make.
• The new scope pushes MCP into presentation and workshop workflows, not just canvas manipulation, according to figma's feature list and the linked MCP update page.
• figma's announcement also adds custom font support and image exports, two practical upgrades for teams moving assets between AI tools and final deliverables.
• Availability appears immediate: when asked when the update lands, figma's reply said, "Now."

You can jump straight to Figma's MCP update page, watch the short demo from figma, and the launch post itself splits the release into three new workflow surfaces, Slides, FigJam, and Make.

The biggest change is where the MCP server can act. Instead of stopping at design files, figma's announcement says it now handles two adjacent formats:

• Generate and edit decks in Figma Slides
• Build FigJam boards with data

That gives AI clients a path into presentation drafts and structured whiteboard generation through the same server endpoint described on Figma's MCP update page.

The third workflow is the most interesting for vibe-coders. figma's launch tweet says the MCP server can "roundtrip from code to canvas in Figma Make," which frames Make less as a one-way export and more as a loop between generated code and editable design output.

The evidence here is thin beyond Figma's own wording, but the claim matters because it places MCP inside a code-to-interface workflow, not just a prompt-to-mockup one, as shown in figma's demo video.

Figma bundled two smaller upgrades with the workflow expansion:

• Custom font support
• Image exports

Those are the kinds of boring features that usually decide whether an MCP integration survives first contact with a real brand system. The launch also appears to be live already, because figma's reply to a user answered the rollout question with a one-word timing update: "Now."