What is the figma-fonts MCP server?
figma-fonts, built as figma-font-handler, pairs a Figma Desktop plugin with a local MCP server on port 3056. After cloning and building it, importing the plugin into Figma, and pointing a client at its mcp-server.mjs, an agent gets 6 tools to list, audit, set and replace fonts, including ones only installed locally, not hosted by Figma.
figma-fonts solves a specific gap: Figma's own cloud tools only see fonts Figma itself hosts, not a licensed brand typeface installed only on your machine. This project's plugin reads your local font list and exposes it to an agent.
A small MCP server runs on your machine over port 3056, paired with the plugin running inside Figma Desktop, so everything stays local and no font data leaves the computer.
What it changes in your workflow
- An agent can set or swap a text layer's font to one only installed locally, not just a Figma-hosted web font.
- audit_fonts checks which fonts a design actually uses and flags any that are missing, before a handoff goes wrong.
- replace_font swaps a family across a whole design while keeping each text layer's existing weights and styles.
- execute runs custom script logic inside the plugin sandbox for a font-related edge case with no dedicated tool.
How the pieces connect
| figma-fonts | |
|---|---|
| Plugin | Runs inside Figma Desktop, reads your local font list |
| Server | MCP server on localhost port 3056 |
| Scope | Local machine only, nothing uploaded |
| Register with | Your MCP client, pointed at mcp/dist/mcp-server.mjs |
Who it is for
Best for
- Brand or agency work where a proprietary typeface stays licensed locally instead of being uploaded to Figma's cloud.
- Catching missing fonts in a design before handing it to someone else, with audit_fonts.
- Swapping a font family across many text layers at once while preserving each one's weight.
Not for
- Free, token-less access to Figma's own data for reading and writing a whole design, rather than a local font bridge, is the different problem a separate Figma MCP Bridge solves.
- A larger local Figma bridge with 63 tools spanning whole design systems, rather than this project's 6 font-specific tools, is what F-MCP Bridge sets up instead.
- Converting a Figma design to code and back again through a different local bridge mechanism, rather than managing local fonts, is what Figbridge MCP does instead.
- Designing a whole new page inside Figma from a text prompt, rather than fixing font access on an existing one, is what AIConnect for Figma does locally.
Use it with UiChemy
This server keeps a licensed local typeface usable inside a Figma design. Once that design is finished, UiChemy Figma to WordPress turns it into an editable Elementor or Gutenberg page. Click Get Started on uichemy.com.
Connect Figma Fonts MCP: Use Your Local Fonts in Figma to your AI client
node mcp/dist/mcp-server.mjsClone and build
Clone the repository, then run npm install and npm run build to produce the plugin and server builds.
Import the plugin into Figma
In Figma Desktop, import the plugin manifest under Plugins, Development, so it can read your local font list.
Add the server entry
Use the config above in your client, pointed at the built mcp-server.mjs.
Launch and verify
Launch the plugin inside Figma, restart your client, and check the connection status shown in the plugin's own panel.
Client configuration
{
"mcpServers": {
"figma-fonts": {
"command": "node",
"args": ["mcp/dist/mcp-server.mjs"]
}
}
}What you can do with it
- Local font visibilityExposes fonts installed only on your machine to an agent, not just the fonts Figma's own cloud already hosts.
- Font audit before handoffaudit_fonts flags fonts a design depends on that are missing locally, catching a broken handoff before it happens.
- Style-preserving replacereplace_font swaps a family across a design while keeping each text layer's existing weight and style settings.
- Fully localThe plugin and server both run on your machine over localhost, so no font data or design content is uploaded anywhere.
- Custom script escape hatchThe execute tool runs arbitrary script logic inside the plugin sandbox for a case none of the named tools cover.
- Small, focused tool setSix tools cover the font problem specifically, rather than bundling in broader canvas or layout management.
Tools it exposes
list_fonts
Lists every local font family and its available styles.
audit_fonts
Checks which fonts a Figma design uses and flags any that are missing locally.
set_font
Sets a text layer's font family while keeping its current weight where possible.
replace_font
Replaces one font family with another across a design, preserving per-layer styles.
set_text
Writes text into a node, loading whichever font that text needs first.
execute
Runs custom script logic inside the plugin sandbox for an operation with no dedicated tool.
Frequently asked questions
What is the figma-fonts MCP server?
It is an MCP server paired with a Figma Desktop plugin, built as figma-font-handler, that gives an agent access to fonts installed locally on your machine inside Figma, through 6 tools for listing, auditing and swapping fonts.
How do I install figma-fonts?
Clone the repository, run npm install and npm run build, import the generated plugin into Figma Desktop under Plugins, Development, then point your MCP client's config at the built mcp-server.mjs before restarting it.
Why would Figma need a local fonts tool?
Figma's own cloud tools only recognize fonts Figma itself hosts, so a licensed brand typeface installed only on your machine is invisible to them. This project's plugin reads your local font list and exposes it instead.
Does any font data leave my machine?
No. Both the plugin and the MCP server run locally over localhost port 3056, and the project's own description keeps the bridge local-only, with nothing uploaded to an external service.
Can it check for missing fonts before I share a design?
Yes. audit_fonts reads which fonts a design actually uses and reports which ones are missing locally, which catches a broken handoff before someone else opens it and sees fallback text instead.
Does swapping fonts keep my text styling?
Yes, as far as the tool is designed to. replace_font is built to preserve each text layer's existing weight and style settings while only changing the font family itself across the whole design.
What is the execute tool for?
It runs a custom script inside the plugin's own sandbox, which covers a font-related edge case that none of the five named tools handles directly, without needing a new release of the project.


