Atlas-Docs
Related Servers
Alternatives to Atlas-Docs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to access up-to-date documentation for Python libraries like LangChain, LlamaIndex, and OpenAI through dynamic fetching from official sources.1MIT
- FlicenseAqualityCmaintenanceAn MCP server that searches official documentation for popular libraries, scrapes pages, and returns clean, LLM-ready text.1-
- FlicenseNot gradedqualityBmaintenanceAn MCP server that retrieves and cleans official documentation for popular AI/Python libraries via web search and LLM processing, exposing a get_docs tool.-
- FlicenseBqualityDmaintenanceAn MCP server that fetches real-time documentation for popular libraries like Langchain, Llama-Index, MCP, and OpenAI, allowing LLMs to access updated library information beyond their knowledge cut-off dates.13-
- AlicenseNot gradedqualityCmaintenanceGeneric MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that turns a directory of markdown documentation into searchable, citable tools for AI assistants, enabling them to find, read, and reference specific sections with auditable citations.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: list_docs discovers documentation sets, get_docs_index provides an overview, get_docs_page retrieves specific content, get_docs_full gets everything, and search_docs finds keywords. The descriptions explicitly guide usage, making misselection unlikely.
All tools follow a consistent verb_noun pattern with snake_case: list_docs, get_docs_index, get_docs_page, get_docs_full, and search_docs. The naming is predictable and readable, using clear verbs like 'get', 'list', and 'search' paired with descriptive nouns.
With 5 tools, the count is well-scoped for a documentation server, covering discovery, navigation, retrieval, and search without being overwhelming. Each tool earns its place by addressing a specific need in the documentation workflow, from initial exploration to detailed content access.
The tool set provides complete coverage for documentation access: list_docs for discovery, get_docs_index for navigation, get_docs_page for targeted retrieval, get_docs_full for comprehensive content, and search_docs for keyword-based finding. There are no obvious gaps, and the descriptions guide agents through a logical workflow.