by hyperdrive-eng
An MCP server that provides runtime debugging access to Node.js for Cursor or Claude Code. No external data files are required.
Repository-wide counts · Cached 2025-10-28
The MCP Node.js Debugger MCP server is a publicly available project. Review the upstream repository for installation instructions, supported tools, compatibility, permissions, and current maintenance status.
Configuration, transport, authentication, and runtime requirements vary by project. Open the repository before connecting and use the smallest set of credentials and permissions required.
Open the MCP Node.js Debugger repository to read the latest documentation.
Compare source, connection, and authentication details before choosing an implementation.
View the complete category
upstash
Context7 MCP server providing up-to-date, version-specific documentation and code examples for libraries, enabling coding agents to fetch accurate docs and code snippets. Requires an API key for higher rate limits, passed via CONTEXT7_API_KEY header.
Microsoft Corporation
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. Enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.
feder-cr
AIHawk is an anti detect browser and web browsing agent, open source, with an MCP server for coding agents: undetected, no captchas, no blocks. It requires an OpenRouter API key for the standalone web UI mode, which can be provided via the --openrouter-key flag or the OPENROUTER_API_KEY environment variable or a .env file in the running directory.
Build-time snapshot · Retrieved 2026-10-05
An MCP server that gives Cursor or Claude Code access to Node.js at runtime to help you debug: @hyperdrive-eng/mcp-nodejs-debugger.
https://github.com/user-attachments/assets/c193a17e-b0e6-4c51-82aa-7f3f0de17e1a
https://github.com/user-attachments/assets/adb7321b-3a6a-459b-a5c9-df365710d4d8
Add to Cursor (~/.cursor/mcp.json)
+ {
+ "mcpServers": {
+ "nodejs-debugger": {
+ "command": "npx",
+ "args": ["@hyperdrive-eng/mcp-nodejs-debugger"]
+ }
+ }
+ }
Run a Node.js server in debug mode (i.e. with the --inspect flat)
node --inspect {file.js}
Ask Cursor to debug your Node.js server at runtime
Add to Claude Code
claude mcp add nodejs-debugger npx @hyperdrive-eng/mcp-nodejs-debugger
Start Claude Code
claude
╭───────────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code research preview! │
│ │
│ /help for help │
│ │
│ Found 1 MCP server (use /mcp for status) │
╰───────────────────────────────────────────────────────╯
Run a Node.js server in debug mode (i.e. with the --inspect flat)
# In another terminal
node --inspect {file.js}
Ask Claude Code to debug your Node.js server at runtime
> I'm getting a runtime error in Node.js
{YOUR_RUNTIME_ERROR}
Please help me debug this error at runtime using the nodejs-debugger mcp.
Add to Claude Code
claude mcp add nodejs-debugger npx mcp-nodejs-debugger
Verify connection
> /mcp
⎿ MCP Server Status
• nodejs-debugger: connected
Remove from Claude Code
claude remove nodejs-debugger
Add to Cursor (~/.cursor/mcp.json)
+ {
+ "mcpServers": {
+ "nodejs-debugger": {
+ "command": "npx",
+ "args": ["@hyperdrive-eng/mcp-nodejs-debugger"]
+ }
+ }
+ }
Verify connection:
Remove from Cursor (~/.cursor/mcp.json):
- {
- "mcpServers": {
- "nodejs-debugger": {
- "command": "npx",
- "args": ["@hyperdrive-eng/mcp-nodejs-debugger"]
- }
- }
- }
Run this simple Node.js app: github.com/mdn/express-locallibrary-tutorial:
node --inspect ./bin/www
Ask Cursor to set a breakpoint
Create a book at localhost:3000/catalog/book/create
Watch Cursor capture runtime state
Here is a buggy Node.js server:
node --inspect index.js
Debugger listening on ws://127.0.0.1:9229/2862f5a2-8618-4516-8429-1248b397e9b4
#######################
## THE RUNTIME ERROR ##
#######################
MongooseServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://www.mongodb.com/docs/atlas/security-whitelist/
at _handleConnectionErrors (/Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/node_modules/mongoose/lib/connection.js:1110:11)
at NativeConnection.openUri (/Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/node_modules/mongoose/lib/connection.js:1041:11)
at async main (/Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/app.js:35:3) {
reason: TopologyDescription {
type: 'ReplicaSetNoPrimary',
servers: Map(3) {
'ac-8e6hgk7-shard-00-01.cojoign.mongodb.net:27017' => [ServerDescription],
'ac-8e6hgk7-shard-00-02.cojoign.mongodb.net:27017' => [ServerDescription],
'ac-8e6hgk7-shard-00-00.cojoign.mongodb.net:27017' => [ServerDescription]
},
stale: false,
compatible: true,
heartbeatFrequencyMS: 10000,
localThresholdMS: 15,
setName: 'atlas-5syy8t-shard-0',
maxElectionId: null,
maxSetVersion: null,
commonWireVersion: 0,
logicalSessionTimeoutMinutes: null
},
code: undefined
}
Claude Code debugs the Node.js server at runtime:
> I'm getting a runtime error connecting to mongoose. Please help me debug by checking the value of
the mongodb configs at runtime using the nodejs-debugger mcp.
⏺ I'll help you debug the mongoose connection issue using the Node.js debugger. Let's first understand where the
MongoDB connection is configured.
⏺ Search(pattern: "**/*.js")…
⎿ Found 100 files
⏺ Let's set a breakpoint at the mongoose connection point and continue:
⏺ nodejs-debugger:set_breakpoint (MCP)(file: …
"/Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/app.js",
line: 35)
⎿ Breakpoint set successfully. ID:
2:34:0:file:///Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/app\.js
⏺ Let's list all our breakpoints:
⏺ nodejs-debugger:list_breakpoints (MCP)
⎿ [
{
"file": "/Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/app.js",
"line": 35,
"id": "2:34:0:file:///Users/arthur/Documents/thirdparties/mdn/express-locallibrary-tutorial/app\\.js"
}
]
⏺ Let's try to execute a specific piece of code to check the connection variables:
⏺ nodejs-debugger:nodejs_inspect (MCP)(js_code: "// Get the mongoose module and inspect connection\nconst mongoose = …
require('mongoose');\nconsole.log('Current mongoose version:',
mongoose.version);\nconsole.log('Current mongoose connection state:',
mongoose.connection.readyState);\n// Log connection string safely (without
password)\nconst connectionString = process.env.MONGODB_URI || \n
\"mongodb+srv://cooluser:[email protected]/local_library?retryWr
ites=true&w=majority&appName=Cluster0\";\nconsole.log('Connection string
(masked):', connectionString.replace(/(?<=mongodb\\+srv:\\/\\/\\w+:)(.+?)(?=@)/,
'*****'));")
⎿ Console output:
[log] Current mongoose version: 8.9.5
[log] Current mongoose connection state: 0
[log] Connection string (masked): mongodb+srv://cooluser:[email protected]/local_library?retryWri
tes=true&w=majority&appName=Cluster0
⏺ The runtime error you're seeing in your application is related to MongoDB
Atlas connection issues. Based on your error message, the problem is:
1. You're using placeholder credentials ("cooluser:coolpassword")
To fix this, you have two options:
1. Use a local MongoDB instance by changing line 29-30 in app.js to:
const dev_db_url = "mongodb://127.0.0.1:27017/local_library";
2. Or correctly set up MongoDB Atlas:
- Log into Atlas at https://cloud.mongodb.com
- Go to Network Access and add your current IP to whitelist
- Create proper database credentials
- Update the connection string with real credentials
Which option would you like to proceed with?