Figma-Context-MCP on Windsurf: failed to parse tool input schema for get_figma_data after 0.2.0
On Windows with Windsurf, Figma-Context-MCP stopped working overnight and now returns: Error: failed to get tools: failed to parse tool input schema for tool get_figma_data: json: cannot unmarshal array into Go struct field .properties of type string. Check your configuration. The MCP config was unchanged and worked the day before. What caused this and how do I fix it?
Originally asked on GitHub: https://github.com/GLips/Figma-Context-MCP/issues/107
2 answers
This was a bug in version 0.2.0 of Figma-Context-MCP, which had just been published. The maintainer reproduced the issue locally, pushed version 0.2.1 with the fix, and closed the issue as completed.
The reporter had not changed the MCP config and the setup worked the previous day, so the error was not caused by their JSON config. The maintainer confirmed the issue and the fix locally and asked users to close Windsurf and reopen it. Reopening Windsurf should trigger a redownload of the latest npx package, pulling in 0.2.1 automatically since the config uses npx -y figma-developer-mcp. No config change was required.
If the error persists after restarting Windsurf and confirming 0.2.1 is being used, the maintainer asked users to report back, but no one in this thread did. For similar "failed to get tools" errors with MCP servers, a useful general step is to check that the exact package name in the server command resolves and that the server process is actually restarted, but in this thread the root cause was the 0.2.0 release, not the configuration.
Did this work for you?What @GLips tried on GitHub (Worked)
The maintainer reproduced the schema parse error locally, released version 0.2.1, and confirmed the fix locally. They asked users to close Windsurf and reopen it so npx would redownload the latest version; no user confirmed the result afterward.
Source: https://github.com/GLips/Figma-Context-MCP/issues/107#issuecomment-2827745035 (opens external site)
Did this work for you?
Related questions
- 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?
- Figma-Context-MCP fails to connect in Cline — how to configure it?
- Figma-Context-MCP get_figma_data fails: 'Error fetching file: [object Object]'