Node.js for Non-Programmers: npm, npx, and Why They Keep Appearing

Who this is for: Researchers using Claude Code who encounter npm install, npx, or Node.js references in tutorials or skill installation instructions and don't know what they are or whether they need them.

The short answer

You no longer need Node.js to install Claude Code. The modern installation methods (the PowerShell one-liner, winget, or the Claude Desktop Code tab) bundle everything Claude Code needs internally. You can ignore Node.js entirely for the initial setup.

You will still encounter npm and npx when:

This document tells you enough to handle those situations without getting lost.

What Node.js, npm, and npx actually are

Node.js is a runtime environment — a program that runs JavaScript outside a browser. Claude Code is built on it. You don't need to know this; you just need the runtime present when something requires it.

npm (Node Package Manager) is the tool that comes with Node.js for installing packages. Think of it like pip for Python, or an app store for developer tools. When you run npm install -g something, you are downloading a package and making it available system-wide.

npx is a companion tool that runs a package directly, without permanently installing it. When you see npx skills add ..., you are running the skills tool once, from the internet, without adding it to your system. It is the "just run this" shortcut.

The -g flag in npm install -g X means "global" — install for all projects on this computer, not just the current folder.

Do you have Node.js?

Open a terminal and type:

node --version

If you see v20.x.x or similar — you have it. Skip to the next section.

If you see "command not found" or "not recognized" — you don't have it. Whether you need to install it depends on what you're trying to do:

Installing Node.js (when you need it)

Option A — winget (Windows, recommended):

winget install OpenJS.NodeJS.LTS

Option B — direct download: Go to nodejs.org, download the LTS version, run the installer. Default options are fine.

After installation, close and reopen your terminal, then run node --version to confirm.

The four commands you will actually use

Installing a skill:

npx skills add anthropics/claude-code --skill frontend-design

This is the standard way to add Claude skills from GitHub. npx fetches and runs the skills installer without you needing to install it first. You will see this pattern throughout the skills ecosystem documentation.

Installing an MCP server globally:

npm install -g zotero-mcp

Many MCP servers are distributed as npm packages. The -g flag makes them available from any terminal window. After installation, the MCP server can be referenced in your Claude settings by name.

Running an MCP server without installing (common in config files):

"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-slack"]

Many MCP configurations use npx -y package-name as the command. The -y flag means "yes, download it if not already present." You don't install anything; npx handles it on demand each time Claude Code starts.

Keeping packages up to date:

npm update -g zotero-mcp

Common situations

You find a tutorial online that says:

npm install -g @anthropic-ai/claude-code

This is the old installation method. It still works if you have Node.js, but the modern alternatives (winget install Anthropic.ClaudeCode or the PowerShell one-liner) are simpler and don't require Node.js at all. If you already have Claude Code installed, ignore this instruction.

Claude tells you to run npx skills add ...: Copy and run the command in your terminal. If you get "npx: command not found", install Node.js first (see above), then try again.

An MCP server's README says npm install -g X: Run it in your terminal. The package installs globally. Then add the MCP server to your Claude settings as described in the README — usually a small JSON block to add to .claude/settings.json.

You see npx -y @scope/package in a config file: Leave it as-is. This is a self-contained reference; Claude Code will call npx at startup and npx will download the package on demand. You don't need to install anything manually.

When things go wrong

npx: command not found / npm: command not found Node.js is not installed, or the install did not add it to your PATH. Install Node.js from nodejs.org (check "Add to PATH" during setup on Windows), close and reopen the terminal, then retry.

EACCES: permission denied on Mac/Linux You are trying to install globally without administrator access. Either use sudo npm install -g X (requires your password) or configure npm to use a user-writable directory. Tell Claude the error — it will suggest the appropriate fix for your system.

npm ERR! code ENOTFOUND Network error — npm cannot reach the package registry. Check your internet connection. If you are behind a VPN or institutional proxy, that may be blocking the request.

An old tutorial says to install Node.js before Claude Code Skip that step. Install Claude Code with winget or the PowerShell installer instead. You only need Node.js if you later need npm or npx for skills or MCP servers.

What you don't need to worry about

Understanding JavaScript. Node.js runs JavaScript, but you will never write any. The commands above are the entire surface you need.

Versioning. For installing skills and MCP servers, any recent LTS version of Node.js works. If you have v18 or later, you are fine.

npm vs npx vs yarn vs pnpm. You will occasionally see yarn or pnpm in tutorials — these are alternative package managers. For Claude skill and MCP server installation, npm and npx are always sufficient. Ignore yarn/pnpm references unless a specific tool requires them.

Related