Figma MCP Server Adds Slides and Uploaded Font Support
Figma updated its MCP server on June 16, 2026, with four additions: Slides support, uploaded local font rendering, downloadable assets, and Xcode compatibility. These are infrastructure updates, not a redesign of how AI-assisted design work functions. For teams that have already connected Figma to AI clients via MCP, some of these additions may reduce manual steps in specific workflows.
Source: Figma Release Notes, June 16, 2026. Published June 18, 2026.
What the MCP Server Updates Include
Four specific changes are in this release, according to Figma’s release notes:
- Figma Slides support: External agents can now create and update slide presentations built from Figma templates using the
use_figmatool. This extends MCP access beyond design files to presentation decks built inside Figma. - Uploaded local font support: The MCP server now renders type using fonts uploaded to a Figma account rather than falling back to web-safe approximations. For teams with custom brand typography, this means AI-generated analysis or descriptions should more accurately reflect the actual typefaces in use.
- Downloadable assets: A new
download_assetstool lets agents export files from Figma as JPG, SVG, or PDF. This is an extraction capability — useful if an AI workflow needs to pull deliverables rather than just read or describe design context. - Xcode compatibility: Figma designs can now be brought directly into Xcode via MCP to create new flows and preview screens. This is primarily relevant to iOS teams using Figma and Xcode together.
Why the Font and Slides Updates Are the Most Practically Useful
The uploaded font support matters because typography is central to design fidelity. When an AI assistant describes or analyzes a design using web-safe font fallbacks, the analysis may miss brand-specific spacing, weight, or feel. If a team uses a custom typeface for headings, an assistant seeing the correct font is more likely to give accurate feedback on layout, hierarchy, and visual consistency.
The Slides addition is worth noting for teams that use Figma for presentations alongside design files. If a project brief, client deck, or design narrative lives in Figma Slides, an AI client with MCP access could help summarize it, identify open questions, or assist with handoff documentation — rather than the designer extracting content manually. The exact scope of what agents can do with Slides depends on what Figma exposes through MCP; test with your specific AI client before building this into a workflow.
For more on how Figma’s AI features have been developing, see our earlier piece on Figma Make Custom Skills.
What to Be Cautious About
MCP is still evolving infrastructure, and Figma’s note that “Figmates are using our expanded MCP server” is not the same as a validated workflow recommendation for all teams. A few things worth checking before treating this as an active workflow change:
- Which AI clients support the updated server? MCP compatibility varies by client. Confirm that the tools your team uses have implemented the relevant tool endpoints.
- What data leaves Figma and where? If exported assets or font data pass through an AI client’s API, check the data handling policies for both the AI service and your Figma plan tier.
- Are your fonts licensed for this use? Uploaded fonts may have licensing restrictions. Confirm that the font license permits use in AI-assisted workflows before assuming all brand fonts are accessible through MCP without limitation.
Who This Affects
Teams already using Figma with an MCP-compatible AI assistant — and specifically those with uploaded brand fonts or a Slides workflow — will find the most immediate value in this update. For teams not yet using Figma’s MCP server, or whose AI tools have not been approved for connecting to design systems, this is a release note to track rather than act on now.