Skip to main content
Solved

Figma MCP's recommended usage practices (get_code getting stuck)

  • June 9, 2025
  • 1 reply
  • 408 views

pedro.zaroni

I'm trying to use existing Figma layouts to generate code via Figma MCP and Cursor. In general it's working really well, but I've noticed that when I select the whole screen layout, the `get_code` tool from MCP simply gets stuck or takes minutes to run (but I can't know wether it's stuck or just slow).

 

Is there a recommended way to either make get_code run faster or to use the MCP in a more efficient way?

Best answer by Yarden K

Hi ​@pedro.zaroni,

Glad to hear it’s mostly working well! :) You’re right, get_code can hang on large selections, especially full and heavy screens. It usually depends on how big the frame is, how deep the nesting goes, and how much context is being passed.
 

Best move for now is to build your screen through multiple calls - break it into smaller chunks (like a section or component) instead of selecting the full screen. The context will be smaller, so it should run faster and be easier to work with.
 

We’re planning to make this easier to do directly in Figma (based on beta feedback), so stay tuned!

View original

1 reply

Yarden K
Figmate
  • Figmate
  • 9 replies
  • Answer
  • June 9, 2025

Hi ​@pedro.zaroni,

Glad to hear it’s mostly working well! :) You’re right, get_code can hang on large selections, especially full and heavy screens. It usually depends on how big the frame is, how deep the nesting goes, and how much context is being passed.
 

Best move for now is to build your screen through multiple calls - break it into smaller chunks (like a section or component) instead of selecting the full screen. The context will be smaller, so it should run faster and be easier to work with.
 

We’re planning to make this easier to do directly in Figma (based on beta feedback), so stay tuned!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings