Request for plugin review reconsideration: local-font loading differs from use_figma
Hello Figma Community Support,
The Figma Help Center assistant directed me here and stated that Community Support specialists can route this case to the plugin review team. Please help forward my request for clarification and reconsideration.
Plugin: [redacted by moderator to remove personal information]
Plugin ID: [redacted by moderator to remove personal information]
Resource: [redacted by moderator to remove personal information]
The rejection message states:
“We're not able to approve apps that overlap with native capabilities in the Figma MCP server. Consider building skills on top of the official use_figma tool.”
I understand the concern about overlapping functionality. However, this plugin was developed to address a local-font loading difference observed in testing on October 11, 2026:
1. An existing native text node used the font family “HYDiShengYingXiongTi”, style “J”.
2. The official use_figma workflow could read the node, but loading its original font with figma.loadFontAsync failed.
3. The same font loaded successfully through the plugin running in Figma Desktop on the same computer.
4. Through the desktop bridge, the text was edited while preserving its original font, range-level font sizes, colors, and editability.
The intended workflow uses the official Figma MCP first. The companion Codex skill switches to the desktop bridge only after an actual font-loading failure. An independent Codex test successfully followed this fallback and completed the text edit.
These findings describe the tested environment; they are not a claim that every official MCP configuration has this limitation.
The plugin connects to a companion service on the user’s computer at http://localhost:4789. Font files are not transferred. The current implementation also supports user-approved JavaScript execution, and execution results may include document data returned to the connected AI tool. Users review and approve that code in the plugin before it runs.
Could the review team please clarify:
• Is there a supported way for official use_figma to load fonts available in the user’s Figma Desktop environment when the MCP workflow fails to load them?
• If this desktop-font gap is not currently covered, would a companion focused on that gap be eligible for Community publication?
• Would narrowing the plugin to font-specific operations address the overlap concern? What other changes would be required for reconsideration?
I can provide detailed reproduction steps and a recorded comparison if requested.
Thank you for your guidance.
The plugin developer