doc-bot
Related Servers
Alternatives to doc-bot
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.523 npm36MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to save and retrieve code snippets using semantic vector search, generate language-specific style guides and comprehensive wiki documentation, and orchestrate multi-agent documentation workflows.-
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with professional coding standards, development best practices, and context-aware guidance through static documentation and AI-powered custom recommendations. Enables agents to access comprehensive development guidelines including coding rules, debugging techniques, and AI steering instructions.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to crawl, index, and retrieve information from technical documentation using semantic search, with optional knowledge graph validation for code hallucination detection.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to save and retrieve code snippets, perform semantic code search, generate language-specific style guides and deep wiki documentation, and orchestrate multi-agent workflows for comprehensive documentation.-
- AlicenseBqualityCmaintenanceProvides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.1661 npm2MIT
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: docset management (add, list, remove), documentation retrieval (search, read by file, read by ID, index, refresh), rule creation/update, API deep dive, and guidance. Overlaps are minimal and descriptions clarify boundaries.
Most tools use a consistent verb_noun snake_case pattern (e.g., add_docset, search_documentation). The tool 'doc_bot' breaks this pattern as a noun_noun, but it's a single outlier and still readable.
11 tools is well-scoped for a documentation MCP server. The set covers docset operations, documentation queries, rule management, and guidance without being overwhelming or too sparse.
The tool surface covers the full documentation lifecycle: install/remove docsets, create/update rules, search, read, index, and refresh. Missing operations like document deletion are not clearly needed based on the domain, so no obvious gaps.