NPM Package Docs MCP
Related Servers
Alternatives to NPM Package Docs MCP
- AlicenseNot gradedqualityFmaintenanceFacilitates LLMs to efficiently access and fetch structured documentation for packages in Go, Python, and NPM, enhancing software development with multi-language support and performance optimization.76 npm79MIT
- AlicenseBqualityFmaintenanceA server that helps discover and analyze websites implementing the llms.txt standard, allowing users to check if websites have llms.txt files and list known compliant websites.213 npm78MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that fetches up-to-date, version-specific documentation and code examples from libraries directly into LLM prompts, helping developers get accurate answers without outdated or hallucinated information.82394,752 npm63,985MIT
Related Servers
- FlicenseCqualityDmaintenanceRetrieves documentation for any npm package by automatically discovering its GitHub repository and returning its README.md content.11-
- AlicenseAqualityDmaintenanceProvides comprehensive contextual information about npm packages including README files, versions, dependencies, download statistics, and search functionality. Enables users to explore and analyze npm packages through natural language queries with intelligent GitHub README fetching and branch fallback.9MIT
- FlicenseNot gradedqualityAmaintenanceEnables coding assistants to pull on-demand documentation for any npm package — TypeScript signatures, prose docs, and code examples formatted to match the user's intent (how-to, reference, or migration). It also supports version comparison with real changelog-backed breaking changes, cross-version migration guides, error diagnosis, side-by-side package comparison, and project dependency scanning for outdated, deprecated, or insecure packages.-
- FlicenseNot gradedqualityAmaintenanceDelivers real-time, intent-aware documentation for any npm package, returning TypeScript signatures, prose docs, and code examples directly to AI coding assistants with minimal token usage. It also enables concept-based API search, version and migration comparison, error diagnosis, side-by-side package comparison, and dependency scanning for outdated, deprecated, or insecure packages.-
- FlicenseNot gradedqualityAmaintenanceEnables clients to retrieve real-time framework documentation for any npm package, returning TypeScript types, prose, and code examples with intent-aware formatting, plus version migration guidance, error diagnosis, package comparison, and dependency scanning.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to access real-time, context-aware documentation, TypeScript types, code examples, version and migration guidance, error diagnosis, package comparison, and dependency scanning for any npm package.MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is singular and clearly defined, making disambiguation perfect.
The single tool name follows a clear verb_noun pattern (get_docs_for_npm_package), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool for an 'NPM Package Docs' server feels too thin and under-scoped. The server's purpose suggests potential for more operations like searching packages, listing versions, or getting specific documentation sections, but only one basic retrieval tool is provided.
The tool surface is severely incomplete for the apparent domain of npm package documentation. It only allows getting docs for a package, with no support for operations like searching, filtering, or handling multiple packages, which are likely needed for effective agent workflows.