Skip to main content
Solved

get_design_context MCP tool returns incorrect colors for component instances

  • January 22, 2026
  • 1 reply
  • 133 views
Ali Shouman

get_design_context MCP tool returns incorrect colors for component instances


ISSUE SUMMARY

The get_design_context MCP tool is returning incorrect colors for component instances. Specifically, the Delete button in an Alert Dialog component is showing the wrong background color.


EXPECTED BEHAVIOR

The MCP tool should return the actual colors that are visible in the Figma design for each component instance.


ACTUAL BEHAVIOR

When calling get_design_context on the Alert Dialog component (node ID: 295:240366), the Delete button instance returns an incorrect background color.

The Delete button returns:

    bg-[var(--general/primary,#171717)]

The background color #171717 (very dark gray/almost black) uses the --general/primary CSS variable, which does not match the actual (red) background color visible in the Figma design.


REPRODUCTION STEPS

1. Open the Figma file: https://www.figma.com/design/86EIEM1PRbIGVrBB1nhTJf/Obra-shadcn-ui--Community-?node-id=295-240366&t=HVTZYPp9l36u38aD-4

2. Use the get_design_context MCP tool with node ID: 295:240366 (Alert Dialog)

3. Observe the background color returned for the Delete button (nested instance at I295:240366;14:1343)

4. Compare with the actual Delete button background color visible in Figma


NODE IDS FOR REFERENCE

• Alert Dialog component: 295:240366
• Delete button instance (showing incorrect color): I295:240366;14:1343
• Base button component: 14:1343

 

 

Best answer by ksn

Hey ​@Ali Shouman - thank you for surfacing this. I checked in with the teams that work on MCP, and the message they wanted to pass on was the following:

 

The button instance in the Alert Dialog definition has an unnecessary fill override on it. The MCP server respects and prioritizes that override. If you remove it, it'll still be the right color and the MCP response will respect the danger variant background in your Alert Dialog instance as intended.

 

They have noted this feedback on their end as well, and they are actively discussing how they can make improvements to this in the future.

This topic has been closed for replies.

1 reply

ksn
Figmate
  • ksn
  • Community Support
  • Answer
  • January 27, 2026

Hey ​@Ali Shouman - thank you for surfacing this. I checked in with the teams that work on MCP, and the message they wanted to pass on was the following:

 

The button instance in the Alert Dialog definition has an unnecessary fill override on it. The MCP server respects and prioritizes that override. If you remove it, it'll still be the right color and the MCP response will respect the danger variant background in your Alert Dialog instance as intended.

 

They have noted this feedback on their end as well, and they are actively discussing how they can make improvements to this in the future.

    Terms & ConditionsAccessibility statement