A
licenseNot graded
qualityD
maintenanceProvides LLMs with up-to-date, version-specific documentation and code examples from library sources directly into prompts, eliminating outdated code generation and hallucinated APIs.
807,538 npm
MIT
Context7 MCP
by renCosta2025
Related Servers
Alternatives to Context7 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenancePulls up-to-date, version-specific documentation and code examples for libraries directly into your prompt, preventing outdated or hallucinated APIs.MIT
- AlicenseAqualityDmaintenanceProvides LLMs with up-to-date, version-specific documentation and code examples directly from library sources, eliminating outdated training data and hallucinated APIs by fetching current documentation at prompt time.2807,538 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides real-time, version-pinned documentation from 57+ AI/ML libraries to LLMs, preventing hallucinated APIs by fetching current docs and changelogs directly from GitHub.9 npmMIT
- AlicenseCqualityCmaintenanceProvides real-time access to up-to-date library documentation and code examples for any programming library. Helps AI coding assistants deliver accurate, current information instead of relying on outdated training data.120 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides real-time, up-to-date documentation for major LLM providers (OpenAI, Anthropic, Google Gemini) to prevent hallucinations and outdated code patterns in AI agents.14 npm6MIT
TDQS
A4/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct and non-overlapping purposes: 'resolve-library-id' handles name resolution to obtain a compatible library ID, while 'get-library-docs' fetches documentation using that ID. Their descriptions explicitly define their roles and interdependency, leaving no ambiguity about when to use each tool.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern with kebab-case formatting ('resolve-library-id' and 'get-library-docs'), using clear action verbs ('resolve' and 'get') paired with descriptive nouns. This consistency makes the tool set predictable and easy to understand.
Tool Count2/5
With only 2 tools, the server feels under-scoped for its apparent domain of library documentation retrieval. While the tools cover core resolution and fetching, typical documentation systems might include additional operations like searching, listing libraries, or managing documentation versions, making this set feel incomplete for robust agent workflows.
Completeness2/5
The tool set is severely incomplete for a documentation server, lacking essential operations such as searching for libraries, listing available libraries, or handling documentation updates. It forces a rigid two-step process without alternatives, creating potential dead ends if users need broader exploration or management capabilities.