NodeJS API Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCKER_CONTAINER | No | Flag 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
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-nodejs-modules-api-documentationA | |
| retrieve-nodejs-modules-api-documentationA | Retrieve, fetch, and get Node.js API documentation for a specific module or class. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| nodejs-api-lookup | Search up-to-date knowledge for Node.js modules API Documentation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Node.js Releases Schedule Chart | A chart showing the release schedule of Node.js versions. |
TDQS
Scored across 2 tools
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.
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.
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.
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.