Describe the Bug
Initially, the Figma MCP integration with Cursor worked perfectly—it generated accurate, clean code from Figma designs and saved images correctly. But over the past few days, the design output has become unstable and inconsistent. The generated UI no longer matches the structure or quality of the Figma files—it often misses alignment, spacing, or even component grouping. Moreover, the image download feature (via download_figma_images) no longer saves assets into the current project directory, even though logs say “Successfully called tool.”
I completely uninstalled and reinstalled Node.js, Cursor, and even used a new Figma account and API key. Still, the issue persisted. Even when my friend installed Cursor + Figma MCP for the first time on a clean system, the exact same problems occurred—proving it’s not isolated to just my setup. It seems like the Figma MCP backend or its integration with Cursor has become broken or outdated. This severely impacts workflows relying on accurate design-to-code output.
Steps to Reproduce
Install Cursor IDE (latest version) on Windows 10.
Install Node.js (I used v22.16.0).
Set up Figma MCP using npx -y figma-developer-mcp --figma-api-key=YOUR_KEY --stdio.
Add the MCP JSON configuration in Cursor and start the server.
Use any Figma design (even a simple button or form layout).
Run the “download_figma_images” or generate code from Figma.
Notice:
Code generation becomes inconsistent or messy.
Layouts don’t match the original Figma structure/design.
Image download says “successful” in logs but nothing appears in the current project directory.
Even new installs on other systems (fresh users) face the same problems.
Expected Behavior
Cursor should generate clean, accurate, and responsive code that closely matches the Figma design.
It should download all Figma assets (images, SVGs, etc.) into the currently opened project directory automatically.
The design output should maintain layout integrity, spacing, and component structure as shown in Figma.
It should work the same way every time—even on a fresh install or on another machine.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.5 (user setup)
VSCode Version: 1.96.2
Commit: ef5eeb47a684b4c217dfaf0463aa7ea952f8ab90
Date: 2025-06-21T05:31:17.701Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.17763
Additional Information
I’ve tried completely uninstalling and reinstalling Node.js, Cursor, and MCP. Even with a fresh setup and valid Figma API keys, the bug persists.
I tested this on different Figma files and even my friend who used Cursor for the first time experienced the same issue.
We also confirmed that the images are being saved in the default system folder (C:\Users<User>\assets\images) instead of the project directory.
No proxies or VPNs were used, and internet connection was stable.
This issue started recently—Cursor worked perfectly before. Now, both image downloading and design output quality have degraded.
Tested on Windows 10, multiple machines.
Does this stop you from using Cursor
No - Cursor works, but with this issue
