Connect NodeLens to Claude Desktop so Claude can read all your Blueprints directly — no copy-paste required. One setup, full project context.
The NodeLens MCP server requires Node.js. If you don't have it installed, download the LTS version from nodejs.org and run the installer.
To verify it's installed, open a terminal and run:
node --version
You should see a version number like v20.x.x.
Open NodeLens and go to Settings. Find the Projects Directory field and copy the path — you will need it in the next step.
Open Claude Desktop and go to Settings → Developer → Edit Config. This opens claude_desktop_config.json.
Add the following entry inside "mcpServers", replacing the two paths with your own:
{
"mcpServers": {
"nodelens": {
"command": "node",
"args": [
"C:\\Path\\To\\NodeLens\\mcp-server\\index.js",
"C:\\Path\\To\\Your\\Projects"
]
}
}
}
The first path is the mcp-server\index.js file inside your NodeLens installation folder. The second path is the Projects Directory from Step 2.
\\) in JSON, or forward slashes (/) — both work.
Save the config file and fully restart Claude Desktop (quit from the system tray, then reopen). Claude will start the MCP server automatically on launch.
To verify it's working, look for a 🔌 nodelens indicator in Claude Desktop, or ask Claude:
List my NodeLens projects.
Claude should respond with the projects in your Projects Directory.
Make sure the Projects Directory path in the config matches exactly what's set in NodeLens Settings. Even a trailing slash difference can cause issues.
Check that Node.js is installed and accessible from the terminal (node --version). Also verify that the path to index.js is correct and the file exists.
The config file must be valid JSON. Common mistakes: missing comma between entries, single backslashes instead of double (\\), or a trailing comma after the last item. Use a JSON validator if unsure.