MCP server fails to fetch Figma file data due to missing fetch in Node.js environment

[chienchuanw]

Describe the bug
When attempting to fetch Figma file data using the MCP server, the operation fails with the following error message:
Error fetching file: Error: The MCP server is being run in a Node.js environment where fetch is not available. You won't be able to access any data related to the Figma file.

To Reproduce
Steps to reproduce the behavior:

1. Start the MCP server using Node.js
2. Trigger a Figma-related action (e.g., fetching file or node)
3. Observe the error in the console output

Expected behavior
The MCP server should successfully fetch the Figma file data, given a valid fileKey and nodeId.

Screenshots

Server Configuration
Provide your MCP JSON configuration, if applicable. E.g.

   "figma-developer-mcp": {
  "command": "npx",
  "args": [
    "figma-developer-mcp",
    "--figma-api-key=REDACTED",
    "--stdio"
  ]
}

Command Line Logs

> npx figma-developer-mcp --figma-api-key=REDACTED

Configuration:
- FIGMA_API_KEY: ****8pXg (source: cli)
- PORT: 3333 (source: default)

Initializing Figma MCP Server in HTTP mode on port 3333...
HTTP server listening on port 3333
SSE endpoint available at http://localhost:3333/sse
Message endpoint available at http://localhost:3333/messages
New SSE connection established

MCP Logs
mcp-server-Framelink Figma MCP.log

Additional context
Add any other context about the problem here.

[a3660980]

+1

[chienchuanw]

@a3660980
Well there is one thing I have noticed. If you are using nvm with multiple Node installed, it is possible for Claude Desktop to use the oldest node along with MCP server. So what I did is to uninstall all Node except Node 22 in nvm. And the problem got solved.
Perhaps, you could try this trick to see whether it works or not.

[a3660980]

@chienchuanw
我剛剛改成用
https://www.npmjs.com/package/@hapins/figma-mcp

成功了ＸＤＤ

[GLips]

This is an odd one that I've encountered myself. I think Claude Desktop doesn't load the right version of Node from NVM (or whatever package manager you're using) out of the box. I had to create an npx-for-claude command and stick it in /usr/local/bin/, then use that in the Claude desktop instead of just npx.

This is what worked for me—

Add /usr/local/bin/npx-for-claude file:

#!/bin/zsh
source ~/.zshrc
exec npx "$@"

Run chmod +x /usr/local/bin/npx-for-claude to make the file executable.

Update your Claude config:

{
  "mcpServers": {
    "Framelink Figma MCP": {
      "command": "npx-for-claude",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ]
    }
  }
}

Let me know if that solves the issue @a3660980 @chienchuanw?

[a3660980]

This is an odd one that I've encountered myself. I think Claude Desktop doesn't load the right version of Node from NVM (or whatever package manager you're using) out of the box. I had to create an npx-for-claude command and stick it in /usr/local/bin/, then use that in the Claude desktop instead of just npx.

This is what worked for me—

Add /usr/local/bin/npx-for-claude file:

#!/bin/zsh
source ~/.zshrc
exec npx "$@"

Run chmod +x /usr/local/bin/npx-for-claude to make the file executable.

Update your Claude config:

{
  "mcpServers": {
    "Framelink Figma MCP": {
      "command": "npx-for-claude",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ]
    }
  }
}

Let me know if that solves the issue @a3660980 @chienchuanw?

It can work! tks

[GLips]

Amazing! Happy coding 😄

[LinDaiDai]

In fact, there is another simpler method, which is to adjust the default version number of the node to 22.
$ nvm alias default 22

[a3660980]

@LinDaiDai It doesn't work. I tried

[chienchuanw]

There one thing you could, at least this is what I did.
Use which -a node to see if there are multiple node path in you machine. If so, this might be one of the reason.
Second, check your nvm and what's the lowest version you have installed. Here is the tricky part, I installed node 22, 21, 16, and set node 22 as my default. But somehow MCP server kept using node 16 for no reason. After I uninstalled all nodes except node 22, my Figma MCP works fine.

[LinDaiDai]

There one thing you could, at least this is what I did. Use which -a node to see if there are multiple node path in you machine. If so, this might be one of the reason. Second, check your nvm and what's the lowest version you have installed. Here is the tricky part, I installed node 22, 21, 16, and set node 22 as my default. But somehow MCP server kept using node 16 for no reason. After I uninstalled all nodes except node 22, my Figma MCP works fine.

After setting the version 22 as the default one through the command "nvm alias default 22", you still need to use the command "nvm use default". Besides, you also need to restart the cursor editor.

[chienchuanw]

There one thing you could, at least this is what I did. Use which -a node to see if there are multiple node path in you machine. If so, this might be one of the reason. Second, check your nvm and what's the lowest version you have installed. Here is the tricky part, I installed node 22, 21, 16, and set node 22 as my default. But somehow MCP server kept using node 16 for no reason. After I uninstalled all nodes except node 22, my Figma MCP works fine.

After setting the version 22 as the default one through the command "nvm alias default 22", you still need to use the command "nvm use default". Besides, you also need to restart the cursor editor.

I am using Claude Desktop instead of Cursor 🙈