A
licenseNot graded
qualityC
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.
354,384 npm
MIT
Context7 MCP
by 3737123Dush
Related Servers
Alternatives to Context7 MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides up-to-date, version-specific documentation and code examples for libraries and frameworks directly into AI prompts, eliminating outdated code generation and hallucinated APIs.2354,384 npmMIT
- AlicenseNot gradedqualityDmaintenancePulls up-to-date, version-specific documentation and code examples for libraries directly into your prompt, preventing outdated or hallucinated APIs.MIT
xenodocs-mcp-serverofficial
AlicenseAqualityCmaintenanceFetches up-to-date, version-specific documentation and code examples for any library, preventing outdated or hallucinated API usage in LLM responses.2MIT- FlicenseNot gradedqualityDmaintenanceProvides up-to-date, version-specific documentation and code examples for software libraries directly to LLMs, enabling resolution of library identifiers and retrieval of relevant documentation with code snippets.-
- FlicenseAqualityDmaintenanceProvides Large Language Models with real-time access to the latest documentation for Python libraries like Langchain, LlamaIndex, and OpenAI, enabling accurate and up-to-date code suggestions.1-
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: 'resolve-library-id' resolves package names to library IDs, while 'get-library-docs' fetches documentation using those IDs. There is no overlap in functionality, and the descriptions explicitly define their roles and interdependencies, making it impossible to confuse them.
Naming Consistency5/5
Both tools follow a consistent verb-noun pattern with kebab-case (e.g., 'get-library-docs', 'resolve-library-id'), using clear action verbs ('get', 'resolve') paired with specific nouns. This consistency makes the tool set predictable and easy to understand at a glance.
Tool Count3/5
With only two tools, the server feels thin for its apparent domain of library documentation retrieval. While the tools cover core functions (resolving IDs and fetching docs), typical documentation servers might include additional operations like searching, listing libraries, or managing versions, suggesting a borderline under-scoped surface.
Completeness4/5
The tool set covers the essential workflow for fetching library documentation: resolving IDs and retrieving docs. However, there are minor gaps, such as no tools for searching libraries directly, listing available libraries, or handling documentation updates, which agents might need to work around but don't break core functionality.
Maintenance
ActivityInactive
ResponsivenessNo issues