# Reported issues for io.github.TranHoaiHung/figma-ui-mcp Pod holds 8 of 8 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [io.github.TranHoaiHung/figma-ui-mcp](/mcp/io-github-tranhoaihung-figma-ui-mcp). ## Most discussed ### Request for PVR - Private Vulnerability Report I found critical vulnerability in this repo, and I'd like to report it. Can you please open PVR (private vulnearbility report) for this repository? thanks [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/15) · 2026-08-17 · open · external user · 0 comments ### Feature Request: Dedicated Skill Template for figma-ui-mcp to Reduce Prompt/Config Boilerplate ## Feature Request First of all, thank you for building `figma-ui-mcp`. The bidirectional workflow between Figma and AI agents is extremely promising and already very useful in real-world development workflows. However, after experimenting with multiple MCP clients such as Claude Code, Codex, Cursor, and VS Code, I noticed that users still need to spend a significant amount of time manually tuning: * `claude.md` * system prompts / rules * Codex instructions * project conventions * component m [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/13) · 2026-05-26 · closed · external user · 0 comments ### Lâu lâu bị disconnect hoài! Sao cứ lâu lâu nó bị disconnect xong phải đợi connect lại, có khi không connect, chạy npx lại cũng không connect được luôn. Kiểu không bị ổn định á anh có cách fix không ạ. [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/12) · 2026-05-20 · closed · external user · 1 comment ### Add a method to filter all invisible elements First of all, thank you for the awesome plugin! I noticed that when the LLM reads data from Figma, it sometimes does not respect the visible: false attribute and still processes elements that are hidden by the designer. It would be very helpful to have a toggle or configuration option to enable/disable filtering of these hidden elements. This would give better control depending on the use case. [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/5) · 2026-04-08 · closed · external user · 1 comment ### Component instance node does not expose explicit component property values **Bug Report** When reading a Figma component instance via `figma_read`, the response does not include an explicit mapping of the instance's component property values. **Steps to reproduce** 1. Create or select a component instance with component properties configured in Figma. 2. Call `get_selection(detail=full, depth=full)` or `get_design(nodeId=, detail=full, depth=...)`. 3. Inspect the returned fields for the instance node. 4. Optionally compare with `get_local_compon [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/4) · 2026-04-02 · closed · external user · 1 comment ### Node data does not expose references to applied text or color styles **Bug Report** When reading Figma nodes via `figma_read`, the response does not include explicit references to applied local styles, even when text or paint styles are clearly used on the node. **Steps to reproduce** 1. Create or select nodes that use local text styles and/or local color styles in Figma. 2. Call `get_node_detail(nodeId=)`, `get_selection(detail=full, depth=full)`, or `get_design(nodeId=, detail=full, depth=...)`. 3. Inspect the returned node fields. * [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/3) · 2026-04-01 · closed · external user · 1 comment ### Instance node does not expose a reference to its source component **Bug Report** When reading a Figma component instance via `figma_read`, the response does not include any explicit reference to the source/main component. **Steps to reproduce** 1. Select a component instance in Figma. 2. Call `get_selection(detail=full, depth=full)` or `get_design(nodeId=, detail=full, depth=...)`. 3. Inspect the returned fields for the instance node. **Expected result** The instance node should include a field pointing to its source component, such as [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/2) · 2026-04-01 · closed · external user · 1 comment ### Bug: multiple session startup in Codex App kills MCP processes and causes `Transport closed` ## Bug: multi-session startup in Codex App kills sibling MCP processes and causes `Transport closed` ### Summary When `figma-ui-mcp` is configured as an MCP server in Codex App, Codex App starts a separate MCP stdio process for each chat/session. The current bridge lifecycle logic can start extra local HTTP bridges on fallback sessions and later kill those processes as "stale". Since the killed PID is the whole MCP process, not just the bridge listener, the affected session loses its stdio tra [Read the thread](https://github.com/TranHoaiHung/figma-ui-mcp/issues/1) · 2026-04-01 · closed · external user · 1 comment ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/TranHoaiHung/figma-ui-mcp/issues).