# Old node in cursor (cursor-server)

**URL:** <https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298>\
**Category:** Bug Reports\
**Tags:** mcp, wsl\
**Created:** [April 17, 2026, 1:35pm UTC](https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298 "2026-04-17T13:35:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Volodymyr\_Lishchyshy](https://avatars.discourse-cdn.com/v4/letter/v/5f8ce5/32.png) [@Volodymyr\_Lishchyshy](https://forum.cursor.com/u/Volodymyr_Lishchyshy)\
**Post date:** [April 17, 2026, 1:35pm UTC](https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298/1 "2026-04-17T13:35:29Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

cursor-server use old node 20.18, but many mcp-s require 20.19 or above.  
in WSL

### Steps to Reproduce

cd ~/.cursor-server/bin/…  
./node -v

### Screenshots / Screen Recordings

 ![Screenshot 2026-04-17 163217.png](https://us1.discourse-cdn.com/cursor1/original/3X/f/e/fe0e9846ad89a408c33c9f151de2d96233e2db07.png)

### Operating System

Linux

### Version Information

Version: 3.1.15 (user setup)  
VSCode Version: 1.105.1  
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80  
Date: 2026-04-15T01:46:06.515Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 17, 2026, 1:48pm UTC](https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298/5 "2026-04-17T13:48:29Z")

</div>

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)](https://forum.cursor.com/t/cursor-remote-runtime-locked-to-node-20-breaks-modern-extensions-requiring-node-22-node-sqlite/151196). 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.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 17, 2026, 1:54pm UTC](https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298/7 "2026-04-17T13:54:27Z")

</div>

Split this topic on April 17, 2026, 1:54pm UTC

A post was merged into an existing topic: [Cursor remote runtime locked to Node 20 — breaks modern extensions requiring Node ≥22 (node:sqlite)](https://forum.cursor.com/t/cursor-remote-runtime-locked-to-node-20-breaks-modern-extensions-requiring-node-22-node-sqlite/151196)

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 17, 2026, 1:54pm UTC](https://forum.cursor.com/t/old-node-in-cursor-cursor-server/158298/8 "2026-04-17T13:54:34Z")

</div>

Closed on April 17, 2026, 1:54pm UTC


