Skip to main content
Tarek-MetaCTO
Tarek-MetaCTO
New Member
August 1, 2025
Solved

Figma MCP not working

  • August 1, 2025
  • 43 replies
  • 32634 views

I have Figma MCP enabled but whenever I go to the MCP server URL I see the following response

 

{"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}
    Best answer by Tom Reem

    Hi everyone,

    I really appreciate you taking the time to share your updates here. I’ve passed your latest replies along to our product team to keep your experience front and center.

     

    A couple of points to help clarify next steps:

    1. If you see the following error, this is coming from the Cursor side. It may turn red after 5 minutes, but it should still function. If you can see “5 tools,” it should be connected.
      Figma MCP Cursor test % curl -s http://127.0.0.1:3845/mcp || echo "Connection failed"
      {"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}
       
    2. If you’re seeing errors in your MCP clients, screenshots of where those appear will help us better understand the behavior — feel free to reply here or send those in directly.

     

    If you’d like a member of our Product Support team to take a closer look at your specific file, please reach out to them directly and include:

    • the link to this Forum thread for context
    • a full-size screen recording of the issue (if possible)
    • a link to the affected file
    • edit access for support-share@figma.com

     

    Thanks again for your patience — your reports are a big help in improving things

    43 replies

    Show previous replies
    Schwepps
    Schwepps
    New Member
    September 8, 2025

    This worked for me:
    claude mcp add figma-dev -- npx -y figma-developer-mcp --figma-api-key=YOUR_API_KEY  --stdio  

    You can generate an API_KEY in your account settings.

      Alexei Polozov
      Alexei Polozov
      New Member
      September 8, 2025

      Figma Desktop App version 125.8.6

      still does NOT work with :

      Version: 1.5.9 (Universal)
      VSCode Version: 1.99.3
      Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
      Date: 2025-08-30T21:02:27.236Z
      Electron: 34.5.8
      Chromium: 132.0.6834.210
      Node.js: 20.19.1
      V8: 13.2.152.41-electron.0
      OS: Darwin arm64 24.6.0
       

        Pedro Garcia Lopez
        Pedro Garcia Lopez
        New Member
        October 24, 2025

        For anyone still running into this issue and you are using devcontainers, here’s what fixed it for me.
        Update your configuration to use the following URL:

        {
          "mcpServers": {
            "figma-desktop": {
              "url": "http://host.docker.internal:3845/mcp"
            }
          }
        }


        After making this change, everything started working properly.
        Hopefully, this helps others — it’d be great if the docs included this option too!
         

        Lior Tabachnik
        Lior Tabachnik
        New Member
        November 5, 2025

        Hey i have different problem when i try to establish connection to cursor

         



        loading tools for infinity time,
         

        "figma" : {

        "url": "http://127.0.0.1:3845/mcp",

        "type": "http"

        }

         

        Yevhen Tienkaiev
        Yevhen Tienkaiev
        New Member
        November 6, 2025

        This guide not working https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/#vs-code

         

        When you click authenticate it says:

        OAuth app with client id 0KZQoOxn4dVQzQ8Ugdudkh doesn't exist

         

        So remote MCP not works.

        Please fix this

          Jason Hsieh
          Jason Hsieh
          New Member
          November 10, 2025

          Hey i have different problem when i try to establish connection to cursor

           



          loading tools for infinity time,
           

          "figma" : {

          "url": "http://127.0.0.1:3845/mcp",

          "type": "http"

          }

           

          Same here

          Figma Desktop App version 125.9.10
          Version: 2.0.54 (Universal)

          gund
          gund
          New Member
          December 1, 2025

          I’m having the issue with MCP in VScode, after authenticating the logs just show `[info] Waiting for server to respond to `initialize` request...` and printing this message constantly.

          Seems like the MCP server never initializes in the VSCode even after authentication was successful…

          MCP config is:

          ```

            "figma/mcp-server-guide": {

                "type": "http",

                "url": "https://mcp.figma.com/mcp"

              },

          ```

          Any ideas?

            GregL
            GregL
            New Member
            December 7, 2025

            This works for me in cursor
             

            {
              "mcpServers": {
                "Figma": {
                  "url": "https://mcp.figma.com/mcp"
                }
              }
            }

             

            BohdanS
            BohdanS
            New Member
            January 7, 2026

            Figma Desktop App version 125.11.6

            still does NOT work:
            ```{"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}```

            Lyudmil
            Lyudmil
            New Member
            January 9, 2026

            I’m having the issue with MCP in VScode, after authenticating the logs just show `[info] Waiting for server to respond to `initialize` request...` and printing this message constantly.

            Seems like the MCP server never initializes in the VSCode even after authentication was successful…

            MCP config is:

            ```

              "figma/mcp-server-guide": {

                  "type": "http",

                  "url": "https://mcp.figma.com/mcp"

                },

            ```

            Any ideas?

            I have same issue 

            Show more replies
            Terms & ConditionsAccessibility statement