Skip to main content
Through Iris
Through Iris
New Member
June 16, 2025
Question

Figma MCP, can't get good results, have tried many things

  • June 16, 2025
  • 15 replies
  • 10148 views

I love the MCP project but am having a really hard time getting good results from it, every time I asking Claude Code or Cursor to style my UI component like the provided link it’d not even close, it was 85%-90% wrong, sometimes really wrong. Making it mostly unusable.

Lots of experience with LLM coding, I know what I’m asking for it with-in their capability. I also recently tried Figma Make where I imported the exact some component, using the exact same prompt and it completely nailed. Figma Make using Claude Sonnet got all the colors right, the fonts sizes, added the exact stroke and rounded corners, it even added roll-over state and correctly guessed my design intent, really amazing! But when I do the same with Claude Code and Figma MCP but it completely fails, adding styles to the wrong components, getting all the fonts wrong, colors are all over the place, etc. I have some theories as to why but would love some feedback and help

Theories

  • 1. Tailwind vs traditional CSS - My first thought was that maybe Figma MCP’s “get_code” function may be providing plain CSS and since I’m using Tailwind Claude Code might have trouble converting it, or defaults to some general Tailwind styles rather than what is in my Figma and Tailwind.config But this can’t be right, I see on the blog post it says “get_code provides a structured React + Tailwind representation of your Figma selection” which is exactly what my codebase uses, it should work.
  • 2. Get_code is failing, get_image is called instead. This seems the most likely, since in the “get_code” command Figma tells the model to also use “get_image” I guess to provide a second reference. And since the MCP is pretty unstable, freezes or stops working, maybe it just fails on get_code but successfully get the image. Most AI models can’t produce actuate styles from only an image.
  • 3. User error - This is also very likely, my account doesn’t offer code_connect, maybe I need to have that. Maybe my design tokens or tailwind config is not setup well for Figma or Claude to use. But I would like to think this MCP will just provide the data and the AI model should be able to apply it. Also each time I try it fails in a different way, if I knew it only worked well with colors or only with padding, I could get more use out of it but everything it doesn’t something completely different.

Thanks for reading, would love ay advice anyone has, thanks

    This topic has been closed for replies.

    15 replies

    Show previous replies
    NoahWang
    NoahWang
    New Member
    July 30, 2025

    I attempted to debug the Figma MCP. Currently, only the functions "get_image" and "get_variable_defs" are working properly, but these two are of no use to me and do not provide any assistance to the entire Vibe Coding. Moreover, both "get_code" and "get_code_connect_map" always result in errors.

      NoahWang
      NoahWang
      New Member
      July 30, 2025

      my current test results:

       

       

      I used MCP inspector for debugging.
      The "get_code_connect_map" function indicated: "Code Connect is only available on the Organization and Enterprise plans";
      The "get_code" function indicated: "MCP error -32001: Request timed out"

        Fabio Masini
        Fabio Masini
        New Member
        August 20, 2025

        Is there any news regarding this problem? get_code constantly stops working and sometimes I can't get it to restart.
        For now I've gone back to Framelink's MCP. In my case, I'm using the integration with Claude Desktop.
        Unfortunately, the logging doesn't provide any meaningful indication either, just "An error occurred while using the tool get_code".
        It would probably be enough to have more detailed logging to better understand the problem.

        Kiichi Sugihara
        Kiichi Sugihara
        New Member
        August 21, 2025

        I’ve also been using Figma MCP and encountered a reproducible issue with the get_code function. In my testing, it consistently fails when the selected element contains annotations. However, if I remove all annotations from the selection, get_code works correctly.

         

        Just wanted to share this in case it’s useful as a reference for debugging or future improvements on the Figma side. I’m not looking for advice or feedback—just hoping this helps with identifying the cause.



        Today’s Figma update has at least solved my problem.
        Thanks! I’ve confirmed that I can successfully retrieve the annotation information as well.


        The image below is an example where I used Figma MCP to fetch information into the Claude Code. I’ve confirmed that the annotation information can be retrieved.

         

          Inocencio Junior
          Inocencio Junior
          New Member
          September 1, 2025

          I'm a trae user. I've identified a problem I'm having and want to share how I solved it. Whenever I use get_code on a component, it extracts the assets into the public/assets folder. However, if I try to run the command in the same folder, mcp fails. To do this, I instructed it to create a folder within public with the component's name whenever extracting a component.

          For example,
          extracting a card that will be used within menu 3 of the dashboard

          Then, when it runs mcp, it will direct it to extract the assets into the public/menu3/assets folder.

          Another problem is that the generated code comes within the mcp response, but my agent rewrote the code within the file, and when it did so, it always created a generic version. So, I'm having to manually copy the code generated by mcp and paste it into the tsx file to accurately reflect what was generated. I hope this can help someone.

          Terms & ConditionsAccessibility statement