Figma MCP | Slides, custom fonts, assets, and Xcode
Figma has expanded its MCP server with four improvements connecting design files to presentations, typography, asset exports, and mobile development. Announced on June 16, 2026, external agents can now create and update Figma Slides, use uploaded fonts, download production assets, and work with Figma designs from Xcode 27 beta.
The Figma MCP server expands across design workflows
The Figma MCP server connects Figma with compatible AI agents and development environments. These connections allow an agent to inspect design context, work with existing components and variables, create editable content, and move selected information between the canvas and other tools.
The latest update extends that workflow beyond Figma Design. Presentations can now be created or refreshed through an agent, uploaded fonts can preserve more accurate typography, assets can be downloaded without a separate manual export, and mobile teams can bring Figma context directly into Xcode.
External agents can create and update Figma Slides
The use_figma tool and the figma-use-slides skill now let compatible external agents work directly with Figma Slides files. An agent can add slides, organize a presentation into sections, update text and shapes, apply a theme, adjust layouts, and write speaker notes.
The resulting content remains editable inside Slides instead of arriving as a static presentation export. This can help teams prepare project kickoffs, design reviews, workshops, product updates, and reusable client presentations while continuing to work with their existing templates and presentation styles.
Uploaded fonts keep generated content closer to the brand
The MCP server can now render text with fonts uploaded to a Figma account instead of replacing them with web-safe approximations. This is useful when an agent creates or updates designs and presentations that depend on a specific brand typeface.
Users can upload supported fonts from their Figma account settings after confirming that they have the necessary rights. Once uploaded, those fonts become available to Figma's MCP tools and agents, helping generated slides and canvas content retain the intended typography.
Agents can download assets directly from Figma files
The new download_assets tool lets an agent retrieve rendered exports and original source images from a Figma file. Supported rendered formats include PNG, JPG, SVG, and PDF, while original uploaded JPG, PNG, GIF, and WebP files can be returned without being rendered again.
This can reduce manual export work when a developer needs icons, illustrations, hero images, presentation graphics, or other production assets. The tool can process several selected nodes in one request and follow the export settings already configured in the Figma file.
Xcode connects mobile design with implementation
The remote Figma MCP server can now be configured in Xcode 27 beta. This gives compatible agents structured access to components, variables, layout information, FigJam content, and other Figma context while developers work on an Apple platform project.
Figma also provides a SwiftUI skill that can translate between Figma designs and SwiftUI code. It can help implement selected screens in an Xcode project or send SwiftUI views back to Figma, supporting design exploration and preview work in both directions.
IMPORTANT: Figma's write-to-canvas capabilities remain in beta and currently require an eligible seat on a paid plan. Xcode integration is supported only in Xcode 27 beta, while editing files also requires the appropriate Figma access permissions.{alertWarning}
Daisuki's Take: What This Means for Web Designers
For web designers, the most useful part of this update is the wider movement of editable content. Design context can now support presentations, asset delivery, typography, and development instead of remaining limited to a single canvas or handoff stage.
We think downloadable assets and uploaded font support address two practical sources of friction. Agents can retrieve the actual graphics needed for implementation while keeping generated presentation and design content closer to the project's visual identity.
The practical takeaway is to treat these tools as workflow accelerators that still require review. Slides need editorial refinement, exported assets need format and optimization checks, and generated code or layouts must still be tested for responsiveness, accessibility, and consistency with the design system.
Sources and Recommended Links
- New in the Figma MCP server: Slides, uploaded fonts, and more | Figma Official Release Notes
- Figma MCP server tools and prompts | Figma Official Developer Documentation
- Xcode and Figma: Set up the MCP server | Figma Official Help Center
