Skip to main content
Question

Figma MCP (get_design_context) hangs indefinitely when slots are nested 3+ levels deep with non-default parameter overrides

  • April 24, 2026
  • 1 reply
  • 15 views
Alan Tam

Based on my testing, when slots are nested 3 or more levels deep and the innermost instance has a modified parameter (e.g., the innermost button has its text parameter changed to a non-default value), the get_design_context tool from Figma MCP (remote MCP) will consistently hang indefinitely and never return data. Nesting of 2 levels or fewer works fine.

Additionally, if the button retains its default parameter values, no hang occurs regardless of how many nesting levels are used.

Tested layer hierarchy: Layer 1 instance slot → Layer 2 instance slot → Layer 3 instance slot → Button with text parameter (changed to a non-default value)
 

 

1 reply

Tom Reem
Figmate
  • Tom Reem
  • Figmate
  • April 25, 2026

Hey ​@Alan Tam — welcome to Figma Forum, and thanks for the thorough write-up. The clear reproduction steps and boundary conditions are exactly what helps us investigate something like this effectively.

I looked into this and it may be a current limitation, but I want to make sure we're following up thoroughly on what you're experiencing. I've opened a case on your behalf with our Technical Quality team so they can dig into this with the engineering team. Please check your inbox for an email from me with next steps on sharing file access securely. Your case number is: 1869694.

A couple of additional things that would help me prioritize this:

  1. Use case: Could you share a bit more about the type of design you're building with this nesting structure?
  2. Workflow impact: Is this blocking a specific workflow, or more of an edge case you caught during testing?

Appreciate your collaboration on this — I'll keep an eye out for your reply.

Terms & ConditionsCookie settingsAccessibility statement