Skip to main content
Question

MCP doesn't return auto-layout props for slots

  • March 9, 2026
  • 2 replies
  • 69 views

Oleh_Shydlovskyi1

I’ve encountered an issue that makes components harder to implement while using slots.
Figma MCP doesn’t return any values for the flex properties, which makes no sense, because you need to manually specify what is already there and is available for other layers and adds more friction to the workflow itself. The annotation property exposing doesn’t work as well for some reason, so the only solution is to describe it using plain text.

Can i get a confirmation that this is an intended logic or bug that will be addressed? 



Attaching example of output for slots, along with annotation that has exposed properties below:

export default function TestSlotComp({ className, prop1stSlot2 = null, prop2ndSlot = null }: TestSlotCompProps) {
return (
<div className={className || ""} data-name="test-slot-comp" data-node-id="2989:4635">
<div className="content-stretch flex flex-col gap-[var(--spacing\/0,0px)] items-start min-w-[1440px] p-[var(--spacing\/0,0px)] relative w-[1440px]" data-name="Breakpoint=Default" data-node-id="2989:4636">
<Frame className="bg-white shrink-0 size-[98px]" />
<div className="bg-[var(--surface\/surface,#f4f2ef)] h-[44px] shrink-0 w-[1440px] relative" data-annotations="1st-slot layout props" data-name="1st-slot-2" data-node-id="2989:4638">
{prop1stSlot2 || null}
</div>
<div className="bg-[var(--surface\/surface,#f4f2ef)] h-[44px] shrink-0 w-full relative" data-name="2nd-slot" data-node-id="2989:4639">
{prop2ndSlot || null}
</div>
</div>
</div>
);
}

 

2 replies

Celyn_L
Figmate
  • Figmate
  • March 11, 2026

Hi ​@Oleh_Shydlovskyi1, Celyn from Figma Community Support here.

Thanks so much for taking the time to share this, and for attaching the screenshot as well — that’s very helpful for context.

I understand that MCP isn’t returning auto-layout properties for Slots in your output, and that the annotation property exposure isn’t reflecting those values either.

I’ve raised this with the relevant team to confirm whether this is expected behavior or something we should investigate further, and I’ll update this thread as soon as I have more information to share.

Thanks again for documenting this so clearly — we really appreciate you flagging it.


Celyn_L
Figmate
  • Figmate
  • March 13, 2026

Hi ​@Oleh_Shydlovskyi1 — thanks for your patience.

We’d like to take a closer look to better understand what’s happening on the backend. I’ve created a support ticket (#1793235) on your behalf so our Technical Quality team can investigate further and assist you directly.

When you’re able, please share the impacted file with support-share@figma.com and grant “Can View” access (this will not impact your billing and will allow us to reproduce the issue with Engineering).

To help us investigate, please include the exact layer or element (node) where this is occurring when you reply to the email — the team will continue working with you there to look into this further.