HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
workbackai
mcp-nodejs-debugger
JavaScript2025–2025
workbackai / mcp-nodejs-debugger · Archived

mcp-nodejs-debugger

🐞 MCP Node.js debugger

3Distinct people
4Mentions
0Explicit recommenders
300GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

🐞 MCP Node.js debugger

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2025-03-20 05:26:05 UTC to 2025-03-22 21:47:59 UTC.

012025-03-20 03:00:00 UTC to 2025-03-20 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 20, 03:002025-03-20 06:00:00 UTC to 2025-03-20 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-20 09:00:00 UTC to 2025-03-20 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-03-20 12:00:00 UTC to 2025-03-20 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-20 15:00:00 UTC to 2025-03-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-20 18:00:00 UTC to 2025-03-20 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-20 21:00:00 UTC to 2025-03-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 00:00:00 UTC to 2025-03-21 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 03:00:00 UTC to 2025-03-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 06:00:00 UTC to 2025-03-21 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 09:00:00 UTC to 2025-03-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 12:00:00 UTC to 2025-03-21 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 21, 12:002025-03-21 15:00:00 UTC to 2025-03-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 18:00:00 UTC to 2025-03-21 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-21 21:00:00 UTC to 2025-03-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 00:00:00 UTC to 2025-03-22 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 03:00:00 UTC to 2025-03-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 06:00:00 UTC to 2025-03-22 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 09:00:00 UTC to 2025-03-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 12:00:00 UTC to 2025-03-22 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 15:00:00 UTC to 2025-03-22 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-03-22 18:00:00 UTC to 2025-03-22 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-22 21:00:00 UTC to 2025-03-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 22, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20, 03:002025-03-20 03:00:00 UTC2025-03-20 06:00:00 UTC101
Mar 20, 06:002025-03-20 06:00:00 UTC2025-03-20 09:00:00 UTC000
Mar 20, 09:002025-03-20 09:00:00 UTC2025-03-20 12:00:00 UTC110
Mar 20, 12:002025-03-20 12:00:00 UTC2025-03-20 15:00:00 UTC000
Mar 20, 15:002025-03-20 15:00:00 UTC2025-03-20 18:00:00 UTC000
Mar 20, 18:002025-03-20 18:00:00 UTC2025-03-20 21:00:00 UTC000
Mar 20, 21:002025-03-20 21:00:00 UTC2025-03-21 00:00:00 UTC000
Mar 21, 00:002025-03-21 00:00:00 UTC2025-03-21 03:00:00 UTC000
Mar 21, 03:002025-03-21 03:00:00 UTC2025-03-21 06:00:00 UTC000
Mar 21, 06:002025-03-21 06:00:00 UTC2025-03-21 09:00:00 UTC000
Mar 21, 09:002025-03-21 09:00:00 UTC2025-03-21 12:00:00 UTC000
Mar 21, 12:002025-03-21 12:00:00 UTC2025-03-21 15:00:00 UTC000
Mar 21, 15:002025-03-21 15:00:00 UTC2025-03-21 18:00:00 UTC000
Mar 21, 18:002025-03-21 18:00:00 UTC2025-03-21 21:00:00 UTC000
Mar 21, 21:002025-03-21 21:00:00 UTC2025-03-22 00:00:00 UTC000
Mar 22, 00:002025-03-22 00:00:00 UTC2025-03-22 03:00:00 UTC000
Mar 22, 03:002025-03-22 03:00:00 UTC2025-03-22 06:00:00 UTC000
Mar 22, 06:002025-03-22 06:00:00 UTC2025-03-22 09:00:00 UTC000
Mar 22, 09:002025-03-22 09:00:00 UTC2025-03-22 12:00:00 UTC000
Mar 22, 12:002025-03-22 12:00:00 UTC2025-03-22 15:00:00 UTC000
Mar 22, 15:002025-03-22 15:00:00 UTC2025-03-22 18:00:00 UTC101
Mar 22, 18:002025-03-22 18:00:00 UTC2025-03-22 21:00:00 UTC000
Mar 22, 21:002025-03-22 21:00:00 UTC2025-03-23 00:00:00 UTC101

What Hacker News says

1 sources

Show HN: Let Claude Code control Node.js debugger

Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a Node JS server in debug mode ``` node --inspect <file.js> ``` or ``` NODE_OPTIONS="--inspect" npm run <command> ``` 2. add the MCP to Claude Code ``` claude mcp add nodejs-debugger npx @hyperdrive-eng
Read the rest
/mcp-nodejs-debugger ``` 3. ask Claude Code to set breakpoints and read runtime state. ```` > I'm getting a runtime error in NodeJS. Please help me debug this error at runtime using the nodejs-debugger mcp. ``` Would appreciate feedback, however big or small! Github: https://github.com/hyperdrive-eng/mcp-nodejs-debugger
9 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.