Skip to main content

I was testing figma code connect with mcp and Cursor and unfortunately found that i cannot refine component that is already connected - because “suggested code” is not returns, it only contains my connected info

I tried to run ‘figma connect unpubish --node’, command returns :

Unpublishing Code Connect files from Figma...

Successfully deleted:
--- (React)
--- (storybook)

* my code is vue

But then mcp again returns my code connect snippet instead of real “react code” as it was before connection

Literally now we are trapped as those components cannot be received from figma dev mcp anymore.
Issue is huge


Have you tried on the latest version? We had a similar issue with SwiftUI, and we used the argument --label=SwiftUI and it worked for us.


I am also seeing the same issue when running `figma connect unpublish` to unpublish all components, and I still have at least one that wont disconnect / unpublish


I have this issue too


Hello ​@serhii_muso and everyone following along — thanks for flagging this. I checked in on this, and our engineering team was able to identify an issue that caused the behavior you’re describing here. A fix was released in the latest version of Code Connect, so updating should help get things working again:

  • If you run npm install @figma/code-connect@latest you should get the update.
  • Running npx figma unpublish --node {URL} now requires a --label flag. In this case, you can pass --label "Vue" to explicitly unpublish it.

If you’re still running into trouble after updating, it’d help to take a closer look at your file. You can share details with our Technical Quality team by filling out this form and including:

  1. a link to the file where this is happening
  2. “Can edit” access for support-share@figma.com
  3. a short screen recording, if possible.

Appreciate everyone’s patience while this was sorted — hope this helps get you unblocked!