feat(mcp-server.js): add NodeJS debugger MCP server and simple package.json #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Other changes
None.
Tested
Not flawless, but works.
Add to Claude Code:
Test MCP server is running
Remove from Claude Code:
Run locally to test:
Known bug, the MCP server only works when a NodeJS server is already running in debug mode. When we add the MCP server, it attaches to the debug session as expected. If we add the MCP server first, and then start a NodeJS server in debug mode, the current MCP server does not find the NodeJS server and does not attach.
Backwards compatibility
N/A
Documentation
To publish to NPM:
Note: Increment the version in
package.json
every time we publish.For organisation scope: https://docs.npmjs.com/creating-and-publishing-an-organization-scoped-package