Figma (local)
BetaA community-maintained server that pulls Figma design files and layout data into the agent with a personal access token. It is not published by Figma.
- Productivity
- Local
- Runs
- On the developer's Mac
- Launched with
- npx
- Platform
- macOS
- Publisher
- Community (GLips)
How it works
Every agent request passes through Ferentin policy before it reaches Figma (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y figma-developer-mcp.
Ferentin's endpoint agent finds Figma (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Figma (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Figma (local)
A community-maintained server that pulls Figma design files and layout data into the agent with a personal access token. It is not published by Figma.
Frequently asked about Figma (local)
- How do I connect Figma (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Figma (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Figma (local) integration generally available?
- The Figma (local) integration is currently beta on Ferentin.
Related integrations
3
MarkItDown (local)
Microsoft's MarkItDown converts local files such as PDFs, Office documents and images to Markdown for the agent.
Memory (local)
The reference knowledge-graph memory server. It saves what the agent chooses to remember to a local file.
Notion (local)
Notion's own MCP server reads and writes pages and databases with an integration token.