Skip to main content
Glama
NodeJS API Docs MCP Server

NodeJS API Docs MCP Server

by lirantal

Usage: Generic CLI

npx mcp-server-nodejs-api-docs

You can debug calls for the MCP Server by inspecting the file mcp-server-nodejs-docs.log in your system's temporary directory (e.g., /tmp on Unix-like systems or %TEMP% on Windows) which this MCP Server writes to.

Related MCP server: PyMCP

Usage: as a Docker container

You can run this MCP Server as a Docker container by using the following command:

docker pull ghcr.io/lirantal/mcp-server-nodejs-api-docs:latest

You can also use the Docker image directly in your MCP Server configuration for various applications, see examples below.

Usage for Claude Desktop:

Edit your Claude Desktop MCP Servers configuration file (located on macOS here: ~/Library/Application Support/Claude/claude_desktop_config.json) and add the following:

on macOS or Linux:

{
  "mcpServers": {
    "nodejs-api-docs": {
      "command": "npx",
      "args": ["-y", "mcp-server-nodejs-api-docs"]
    }
  }
}

for Windows users:

{
  "mcpServers": {
    "nodejs-api-docs": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mcp-server-nodejs-api-docs"]
    }
  }
}

or with the Docker image:

{
  "mcpServers": {
    "nodejs-api-docs": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "--init", "-e", "DOCKER_CONTAINER=true", "ghcr.io/lirantal/mcp-server-nodejs-api-docs:latest"]
    }
  }
}

Usage for Cursor AI:

Edit your Cursor AI MCP file (located at ~/.cursor/mcp.json) and add the following:

{
  "mcpServers": {
    "nodejs-api-docs": {
      "command": "npx",
      "args": ["-y", "mcp-server-nodejs-api-docs"]
    }
  }
}

Development

To build the project with Docker locally run:

docker build -t mcp-server-nodejs-api-docs .

Then run the container as follows for your MCP Server configuration:

docker run -i --rm --init -e DOCKER_CONTAINER=true mcp-server-nodejs-api-docs

Documentation

Contributing

Please consult CONTRIBUTING for guidelines on contributing to this project.

Author

mcp-server-nodejs-api-docs © Liran Tal, Released under the Apache-2.0 License.

Available Tools

2 tools
retrieve-nodejs-modules-api-documentationA

Retrieve, fetch, and get Node.js API documentation for a specific module or class.

<use_case> Use this tool to retrieve Node.js API documentation for a specific module or class. </use_case>

You call the `retrieve-nodejs-modules-api-documentation` MCP tool with the following parameters:
```json
{
  "module": "util",
  "method": "styleText"
}
```

<important_notes> 1. If you don't know the module or class name, you can use the search-nodejs-modules-api-documentation tool to get a list of all Node.js core API modules and their methods to search for it first and then call this tool. 2. This tool will return the documentation for the specified module or class, including its methods and properties. </important_notes>

Inputs: module (required), method.

search-nodejs-modules-api-documentationA
  <use_case>
    Use this tool to search across all Node.js built-in core modules API documentation and get back a list of core modules and their methods when you want to search and look-up Node.js API support
  </use_case>
  <important_notes>
    1. HIGH PRIORITY: *ALWAYS* use this tool first so that you can search for Node.js modules and their methods
    2. Ideally you want to suggest users the use of built-in Node.js API rather than third-party libraries
    3. This tool will return a list of all Node.js core modules and their methods
  </important_notes>
  

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches across all Node.js modules to find relevant documentation, and the other retrieves detailed documentation for a specific module or class. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent snake_case pattern with a verb prefix ('search-' and 'retrieve-') followed by the domain ('nodejs-modules-api-documentation'). The structure is uniform and predictable.

    Tool Count3/5

    With only two tools, the set is minimal but covers the core workflow of searching and retrieving documentation. However, for a domain as broad as all Node.js core modules, a few more tools (e.g., listing all modules without a search) might improve completeness.

    Completeness4/5

    The search tool effectively serves as both a search and listing function, returning all modules and their methods. The retrieve tool provides detailed documentation for a specific module. Together, they cover the essential documentation needs, but there is no explicit tool for browsing modules by category or method signatures.

    Related MCP Connectors

    Related MCP Servers