Main
Use NPX/Local Git mode when you need write access (create/modify frames/components) and the full 100+ tool set as documented in README.
Treat it as design-to-code glue: extract variables/styles, generate changelogs, and run accessibility scans to reduce UI drift between Figma and code.
If you only need read-only exploration, README documents Remote SSE mode (~2 minutes) with a smaller tool surface.
Source-backed notes
- README states NPX/Local Git mode exposes 100+ tools; Remote SSE is read-only with a smaller subset.
- README includes a Claude Code setup example using
claude mcp add ... -- npx -y figma-console-mcp@latestand a Figma access token. - README highlights capabilities like version history, diffs, markdown changelogs, and accessibility scanning (WCAG checks).
FAQ
- Do I need Figma Desktop?: Yes for write workflows — README recommends Figma Desktop for full capabilities; web-only has limits.
- Which setup is fastest?: README lists Remote SSE as ~2 minutes for read-only exploration.
- Is it only for extraction?: No — README includes creation/editing tools and accessibility scanning in NPX/Local modes.