Core Installation
4. Node.js
Install Node.js via nvm with the LTS version. Required for development tools and MCP servers.
2 min read
Node.js is required to run MCP servers and plugins via npx — most community MCPs use this mechanism.
Install nvm (Node Version Manager)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bashReload the shell
source ~/.bashrcInstall nvm (Node Version Manager)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bashReload the shell
source ~/.bashrcInstall nvm (Node Version Manager)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bashReload the shell
source ~/.zshrcIf you use bash instead of zsh, replace ~/.zshrc with ~/.bashrc.
Install fnm (Fast Node Manager)
winget install --id Schniz.fnm -e --source wingetClose and reopen PowerShell, then configure fnm:
Configure fnm in PowerShell
fnm env --use-on-cd --shell powershell | Out-String | Invoke-ExpressionTo make this permanent, add the command above to your PowerShell profile: notepad $PROFILE
Install Node.js LTS
nvm install --ltsActivate LTS version
nvm use --ltsInstall Node.js LTS
nvm install --ltsActivate LTS version
nvm use --ltsInstall Node.js LTS
nvm install --ltsActivate LTS version
nvm use --ltsInstall Node.js LTS
fnm install --ltsActivate LTS version
fnm use --ltsCheck Node
node --version # v22.x+Check npm
npm --version # 10.x+Check npx
npx --version # 10.x+Why nvm/fnm instead of the site installer?
- Version managers let you switch versions easily
- Avoid permission issues with
sudo npm install -g - They are the community-recommended standard for development