Node's standard library moves between major versions, and a model will state a signature from its training data with exactly the same confidence as a current one. Searching the real documentation and pulling the specific method closes that gap at the moment it matters, while the code is being written. There is nothing to configure and nothing to authorise, so it is cheap to leave connected.
A small server over the Node.js built-in module documentation, with two tools: search all core modules for the methods that match a question, then retrieve the documentation for a specific module or one of its methods.
- search-nodejs-modules-api-documentation searches across every Node.js core module's API documentation and returns the modules and methods that match the question
- retrieve-nodejs-modules-api-documentation fetches the documentation for a named module, or for one specific method on it
- Answers come from the Node.js API documentation itself rather than from a model's recollection of what it used to say
- Calls are written to mcp-server-nodejs-docs.log in the system's temporary directory, so a lookup that returned nothing useful can be inspected afterwards
Published as mcp-server-nodejs-api-docs and launched over stdio with npx, or run from the ghcr.io/lirantal/mcp-server-nodejs-api-docs container image. No credentials, no configuration and no account.
One command — npx -y mcp-server-nodejs-api-docs