Enables agents to inspect, search, create, and edit text layers in Figma Desktop using fonts installed locally on the computer, without uploading those fonts to Figma. It supports reading selected text and font details, finding exact local font family/style names, creating text layers with installed fonts, and applying batch edits while preserving unchanged formatting.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Agent Font Access Make the selected heading 24pt but keep its current font."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agent Font Access lets agents create and edit Figma text using fonts installed on your computer, without uploading those fonts to Figma. It pairs a local MCP server with a companion plugin in Figma Desktop.
Use Figma’s official MCP for surrounding layout and screenshots. The desktop workflow has been tested on macOS.
The Figma companion is installed through a development import. Either the agent plugin or standalone npm package can prepare its files for you.
Use Agent Font Access when Figma Desktop can use a font that your agent’s remote Figma tools cannot load. As of October 2026, Figma’s remote MCP can access fonts uploaded to a Figma account, but cannot access fonts installed only on your computer. Account uploads are another option if your account supports them. See Figma’s MCP server FAQ.
Related MCP server: figma-ui-mcp
You need Node.js 24 or later, Figma Desktop with edit access to a file, and the required fonts installed locally.
Install the agent plugin for Claude Code or Codex to get the skill, local server, and Figma companion setup files together. The standalone setup below works with other MCP clients.
For Claude Code, install from the repository marketplace.
claude plugin marketplace add nweii/figma-local-fonts-mcp
claude plugin install agent-font-access@agent-font-access --scope userFor Codex, follow the marketplace and desktop installation steps.
For an MCP client with a setup form, use either npx or bunx.
Command | Arguments |
|
|
|
|
Follow standalone setup to register the server and prepare the Figma companion without cloning this repository. Use source setup for development.
Ask the agent to call figma_local_fonts_status and run its prepareCommand if preparation is needed. The command returns the full manifest path.
In Figma Desktop, select Plugins → Development → Import plugin from manifest… and choose that manifest. Import it once per installation.
Open the intended file and run Plugins → Development → Agent Font Access. If the companion is already open, click Find agent sessions.
Ask the agent to call figma_local_fonts_status. It should list the intended file.
Select a text layer and ask the agent to inspect it. Confirm that the returned text and font match your selection.
Keep the companion window open while inspecting or editing. Closing it disconnects the file. You can collapse its details into a compact status panel without disconnecting.
Set up Agent Font Access for my local MCP client using README.md#installation. Preserve an existing working registration. Call status and follow its setup actions, including prepareCommand when present. Keep the installation credential private. Prepare the files before giving me the full manifest path and Figma import steps. After the companion opens in my intended file, verify that status lists that file and inspection returns my selected text and font. Report the checks that passed and any remaining manual step. Ask before testing a write on a disposable duplicate.Select text in Figma, or give the agent a node link, then ask for a change such as “Increase the selected heading to 24 while keeping its font.” For existing text, the agent inspects it before applying changes against its returned revision. For new text, the agent identifies the intended parent and exact local font, then creates the layer with that font already loaded.
Tool | Purpose |
| List connected desktop files |
| Read selected or specified text, including fonts, styles, dimensions, and revisions |
| Find exact font family and style names available in Figma Desktop |
| Create a text layer directly with its installed font, position, color, and wrapping dimensions |
| Apply a batch of changes using each target’s inspected revision |
Edits preserve formatting that the request does not change. The plugin checks every target and loads all required fonts before writing. A failed font load creates no layer. For edits, a preflight failure leaves the batch unapplied; a runtime failure can leave a partial batch. Check every returned state before continuing. Figma Undo can reverse the batch.
See text operations and limits for copy replacement, mixed styles, batch limits, and wrapping dimensions. The agent skill provides setup, routing, and recovery guidance. It is included in the agent plugin; standalone MCP registration does not install it.
If the agent’s server starts after the companion, click Find agent sessions. Ask the agent to check figma_local_fonts_status for setup actions.
See troubleshooting for missing connections, unavailable fonts, stale revisions, partial edits, and conflicting server builds.
The bridge connects only through this computer's loopback interface. It makes no requests to hosted services and does not upload font files. Text, styles, and file metadata returned through MCP reach the agent client and provider you use. Figma's normal document sync still applies.
See privacy and local storage for stored files, credentials, and data handling.
If you installed the agent plugin, remove Agent Font Access through your client's plugin manager. The CLI equivalents are below.
claude plugin uninstall agent-font-access@agent-font-access --scope user
codex plugin remove agent-font-access@agent-font-accessIf you registered the standalone MCP, remove that registration instead.
claude mcp remove --scope user figma_local_fonts
codex mcp remove figma_local_fontsClose the companion and remove its development entry in Figma. Close agent sessions still using the server so the shared broker can stop. Removing a registration leaves the installation credential and paired companion files on disk. See local storage for their locations. Move that directory to Trash if you want to remove those files too. Source checkouts and npm caches are separate from these files.
Run the checks from the source repository directory.
npm run check
npm run build
npm testRun npm run check:release to install and exercise the npm archive, check the bundled agent servers, and assemble review archives under release/. This check uses npm, Bun, Claude Code CLI, zip, and unzip. It downloads npm dependencies and prepares temporary paired files; it does not publish.
The tests cover text preservation, direct creation, MCP routing, and connection recovery. For a live check, use a disposable layer, verify its text and font, then remove it.
Follow release instructions to publish through GitHub Actions and npm trusted publishing.
After source changes, build again and restart the MCP clients and shared broker so they load the rebuilt code. Reopen the Figma companion to load its generated files. See development restart instructions.
For setup problems, start with troubleshooting. Report reproducible bugs in GitHub issues, with the package version, operating system, client, and steps to reproduce. Use fictional text in examples and keep credentials and paired UI files out of reports. For vulnerabilities, follow security reporting.
The implementation and documentation were developed with AI coding agents under human direction.
MIT © 2026 Nathan Cheng.
This server cannot be deployed
The Figma MCP server brings Figma design context directly into your AI workflow.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Agent-Native design tool - create and edit visual designs with agent assistance
Brand-safe MCP for AI agents to create editable, on-brand graphics and automate variants.
