MCP100 verdict
Not currently recommended. Promising for supervised workflows that bridge a Figma document to an MCP client, provided access is limited to files suitable for the connected model.
MCP100 Assessment
Editorial verdict
Promising for supervised workflows that bridge a Figma document to an MCP client, provided access is limited to files suitable for the connected model.
Reviewed 2026-08-11 · Next review 2026-09-10
Task Fit
Mapped
Specialized workflows
Trust
Status warning
tool_contract; install_supply_chain; advisory_freshness
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Inspecting and operating the publisher-documented Figma bridge during design-to-code or design-automation work
Not ideal for
- Replacing designer review or guaranteeing production-ready code and pixel accuracy from arbitrary Figma files
Avoid if
- The connected Figma file contains confidential designs, comments, assets, or data that must not reach the MCP client
Trade-offs
- Live design context reduces screenshot guesswork, while the bridge and Figma-side setup add moving parts and expose document content to the agent.
Evidence scope
Evidence
Popularity
484 MCP repository stars
No MCP-specific package metric is stored
Stars observed 2026-08-14T18:46:26.000Z · Downloads observation date unavailable
Exact implementation repository metric.
No exact package is documented.
Maintenance
Publisher activity observed 2026-08-10T08:09:29Z
Current source snapshot
Trust review
Source relationship: Community implementation
Reviewed 2026-08-11 · Next review 2026-09-10