Is FigmaMCP's source code public?
No. The code that builds FigmaMCP is kept in a private repository. What is public is the built Mac app itself: every release, with a checksum you can verify, in a separate public repository that anyone can browse or file an issue against.
What is private, and what is public
| Part | Status |
|---|---|
| Source code | Private. Not published. |
| Built Mac app and release notes | Public, at the releases repository, with a SHA-256 checksum per download. |
| Issue tracker | Public. File or read issues without needing the code. |
| Upstream project | Public. FigmaMCP is a fork of figma-edit-mcp by Neo Product LLC, first written by sonnylazuardi. |
| Price | Free. See pricing. |
Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB
Why keep the code private but the app free
Those are two separate decisions. Keeping the app free and local avoids Figma’s hosted call limits, which is the whole point of how FigmaMCP talks to the Plugin API instead of a hosted server. Keeping the code private is a separate choice about how the project is maintained; it does not change what the app does, what it costs, or what data it sends, which the privacy page lists in full.
How this compares with the upstream project
FigmaMCP started from figma-edit-mcp, which is public. FigmaMCP has since added its own installer, update checks, anonymous usage counts and a plugin connection flow; see the changelog for what has shipped. The two projects are not kept in sync, and this site covers FigmaMCP, not the upstream project.
Questions
Is FigmaMCP's source code public?
Can I read the code myself?
Where do releases come from, if the code is private?
Is FigmaMCP affiliated with Figma, Inc.?
Last updated: