Skip to main content
Glama
lirantal

NodeJS API Docs MCP Server

by lirantal

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCKER_CONTAINERNoFlag to indicate if running in a Docker container

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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>
  
retrieve-nodejs-modules-api-documentationA

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

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

Prompts

Interactive templates invoked by user choice

NameDescription
nodejs-api-lookupSearch up-to-date knowledge for Node.js modules API Documentation

Resources

Contextual data attached and managed by the client

NameDescription
Node.js Releases Schedule ChartA chart showing the release schedule of Node.js versions.

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues