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
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:
npm install -g figma-developer-mcp- 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--stdiowith 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?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--stdiowere joined without a space.Source: https://github.com/GLips/Figma-Context-MCP/issues/155 (opens external site)
Did this work for you?What @albanx tried on GitHub (Worked)
A commenter installed the package globally with
npm install -g figma-developer-mcpand used a Cline config that callsfigma-developer-mcpdirectly with separate args--figma-api-keyand--stdio.Source: https://github.com/GLips/Figma-Context-MCP/issues/155#issuecomment-2925337028 (opens external site)
Did this work for you?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
--stdioin the reporter's config.Source: https://github.com/GLips/Figma-Context-MCP/issues/155#issuecomment-2930018418 (opens external site)
Did this work for you?
Related questions
- Figma MCP server fails in Cursor: timeout, Client closed, or 403 errors
- Figma-Context-MCP: \"Invalid path specified. Directory traversal is not allowed.\" when downloading images?
- Figma-Context-MCP: RangeError: Invalid string length when fetching large Figma files
- How to use Figma-Context-MCP with VS Code and GitHub Copilot?
- Figma-Context-MCP: why does my AI host pick the wrong tool, and what changed in v0.1.6?