Hey, this is a known issue. The remote cursor-server uses Node.js 20.18.2, while the desktop client is already on Node 22.x. Because of this, MCP servers and extensions that require a newer Node version don’t work in WSL or SSH environments.
There’s already a detailed report about it here: Cursor remote runtime locked to Node 20 — breaks modern extensions requiring Node ≥22 (node:sqlite). The team is aware, but there’s no ETA yet.
As a workaround for MCP servers, you can try setting the full path to your system Node version 20.19 or newer in the MCP server config, so it won’t rely on the built-in Node in cursor-server.
Let me know if the workaround helps.