This MCP server provides access to the official Node.js API documentation through MCP tooling. It fetches and exposes Node.js docs, and offers built-in tools for querying modules, classes, and methods, along with a search tool (node-search) and a list tool (node-list) that help you discover available modules and their members. The server runs over standard input/output (stdio), so you connect to it from MCP clients like Cursor or Qodo AI by launching the server process and wiring stdio to the client.

To use it, start the server (for example with npm run start or by invoking node index.js directly). Once running, you can invoke the node-search tool to find modules or list their methods, or use node-list to get a summary of all available modules. Debug logs are written to /tmp/mcp-server-nodejs-docs.log, which you can tail to diagnose issues. When using an MCP client, configure the client to execute the server command (e.g., node /path/to/index.js) with stdio connected so commands and responses flow through the MCP protocol.

Prerequisites:

• Node.js and npm installed on your system
• Access to the repository or a downloaded copy of the MCP server

Installation steps:

1. Clone the repository (if applicable) and navigate into the project directory: git clone <repository_url> cd <repository_directory>

2. Install dependencies: npm install

3. Start the server: npm run start

   or directly

   node index.js

4. Optional: run in debug mode to enable verbose logging: node index.js --debug

5. Test the built-in MCP inspector tool (if available): npm run debug or npx -y @modelcontextprotocol/inspector node index.js

Notes:

• Ensure Node.js and npm versions are compatible with the project requirements.
• The server will log to /tmp/mcp-server-nodejs-docs.log by default when configured as shown in the mcp_config.

Tips and considerations:

• The server exposes the Node.js API documentation through MCP tools such as node-search and node-list. Use node-search to locate modules or functions, and node-list to get a summary of modules and their available methods.
• Logs are written to /tmp/mcp-server-nodejs-docs.log. Monitor this file for fetches, tool executions, and errors.
• Since the server communicates over stdio, ensure your MCP client is configured to launch the server process and connect its stdin/stdout accordingly.
• If you modify the server paths, update the command in the MCP client configuration to point to the correct index.js path.
• If you run into port or IO errors, verify that your environment permits creating and writing to /tmp, and that no other process is occupying the expected stdio endpoints.