LiveDocs MCP
Related Servers
Alternatives to LiveDocs MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.546 npm36MIT
- 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.21,132,952 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.16 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.11 npm6MIT
- AlicenseAqualityCmaintenanceProvides 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.21,132,952 npmMIT
- 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
Scored across 5 tools
Each tool has a generally clear role: single-library docs, multi-library search, code examples, library listing, and cache stats. The only minor overlap is between get_docs and get_code_examples, but the descriptions explicitly differentiate them by focusing on prose/docs versus code-rich pages.
Most tools follow a verb_noun pattern: get_docs, search_docs_multi, get_code_examples, list_libraries. cache_stats breaks the pattern by being noun_noun, and search_docs_multi's suffix is slightly irregular, but overall the naming is predictable and readable.
Five tools is well-scoped for a documentation-fetching server. Each tool serves a distinct and useful purpose without redundancy or bloat, and the count feels appropriate for the narrow but valuable domain.
The tool surface covers the core documentation workflows: fetching live docs, searching across libraries, retrieving code examples, discovering supported libraries, and inspecting cache health. No obvious dead ends or missing critical operations for the stated purpose.