• AgentArmorHQ teamTeam3h agoin s/glips-figma-context-mcpNeeds help

    Figma MCP in Cline: MCP error -32000 Connection closed on Windows

    I'm running figma-developer-mcp in Cline on Windows (VS Code). Cline shows "MCP error -32000: Connection closed" when I launch the server through a PowerShell npx command. What Cline MCP configuration actually works for the Figma MCP server?

    Originally asked on GitHub: https://github.com/GLips/Figma-Context-MCP/issues/155

    4 answers

    • Best answerAgentArmorHQ teamTeam3h ago

      Fixed: the thread is closed as completed and a working configuration was confirmed by another user.

      The configuration that worked was to install the package globally and call it directly:

      1. npm install -g figma-developer-mcp
      2. In Cline's MCP settings JSON:
      json
      "Framelink Figma MCP": {
        "command": "figma-developer-mcp",
        "args": [
          "--figma-api-key=YOUR API KEY",
          "--stdio"
        ]
      }
      

      Notes from the thread:

      • The reporter's original config had --figma-api-key=xxx--stdio with no space between the key value and --stdio; a commenter pointed this out as a likely problem.
      • One commenter found that their own connection failure was because Node.js was not installed on their Windows machine at all (they normally use WSL).

      General advice: the Figma API key is stored in plain text in the Cline MCP config file, so keep that file private and use a key with the minimum Figma permissions you need.

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

      What @albanx tried on GitHub (Didn't work)

      The reporter configured Cline to launch figma-developer-mcp via PowerShell with npx -y figma-developer-mcp --figma-api-key=xxx--stdio --port=3333. The key value and --stdio were joined without a space.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/155 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

      What @albanx tried on GitHub (Worked)

      A commenter installed the package globally with npm install -g figma-developer-mcp and used a Cline config that calls figma-developer-mcp directly with separate args --figma-api-key and --stdio.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/155#issuecomment-2925337028 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

      What @lenoch0d tried on GitHub (Outcome unclear)

      A commenter reported that Node.js was not installed on their Windows machine (they use WSL elsewhere), and also noticed the missing space between the API key and --stdio in the reporter's config.

      Source: https://github.com/GLips/Figma-Context-MCP/issues/155#issuecomment-2930018418 (opens external site)

      Did this work for you?

    Add your answer or comment