Self-hosted Figma MCP alternatives
Figma's MCP server is hosted only: it runs as a remote endpoint, with no build you install and run yourself. If you need the server process and its credentials on your own machine, you have to pick a different one.
Every server below installs locally and talks to your agent over stdio. For reading design files specifically, Framelink and Penpot are the local options; the rest cover the reference reading, notes, chat, and structured data around a design, each running from a process you control.
The 8 best self-hosted alternatives
Framelink's community server runs locally and feeds clean layout and styling context from any Figma file to a coding agent, the self-hostable way to keep reading Figma files where Figma's own server cannot run on your machine.
Set up Framelink Figma MCP →Penpot's official server installs locally and reads and manipulates open-source design files, with overview, inspect, export shapes, and plugin code, the local design tool when you want both the server and the files on your side.
Set up Penpot →Useful for reading specs or reference pages beside a design without a hosted process, Fetch runs locally and pulls a URL into clean markdown.
Set up Fetch →The Memory reference server runs on your machine and keeps a local knowledge graph across sessions, holding design decisions an agent should remember, though it does not touch design files.
Set up Memory →The Time reference server runs locally and gives current-time lookups and timezone conversion, a small utility for scheduling around a design project.
Set up Time →Run it yourself and the community Slack server reads history, DMs, and search over stdio with no workspace bot, reaching the design-review conversations from a local process.
Set up Slack →For design assets or specs kept as structured records, the maintained Airtable server runs locally, inspects a base schema, then reads, searches, and writes records, fields, and comments.
Set up Airtable →If the design notes live in documents, the Coda server runs on your own machine and connects an agent to docs, pages, tables, and rows for reading and editing.
Set up Coda →
How to choose
Since Figma's server is hosted only, none of these is a drop-in, but Framelink and Penpot are the self-hostable ways to keep reading and editing design files locally. The rest, Fetch, Memory, Time, Slack, Airtable, and Coda, run on your own machine for the reference reading, notes, chat, and structured data around a design. Self-hosting controls where the process and tokens live; data still travels to each product's API.
FAQ
- Can the Figma MCP server be self-hosted?
- No. Figma offers only a hosted server reached as a remote endpoint, with no self-installable build. If running the server yourself is required, Framelink's community Figma server or Penpot's official server both run locally over stdio.
- Which local server can still read Figma files?
- Framelink. Its community server installs locally and feeds layout and styling context from any Figma file to a coding agent, so you can keep reading Figma files from a process you run, even though Figma's own server cannot be self-hosted.