Documentation Search MCP Server
Related Servers
Alternatives to Documentation Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that scrapes, indexes, and searches documentation for third-party software libraries and packages, supporting versioning and hybrid search.5501,724MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that fetches up-to-date, version-specific documentation and code examples from libraries directly into LLM prompts, helping developers get accurate answers without outdated or hallucinated information.2807,53861,901MIT
- AlicenseNot gradedqualityDmaintenanceA server that provides organized documentation content for various applications using the Model Context Protocol, enabling AI assistants to access quickstart guides and code examples.MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server that provides AI coding agents with real, live, source-cited documentation for npm, PyPI, and Cargo packages, including READMEs, metadata, vulnerability checks, and package search.577MIT
- FlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol server that enables searching and retrieving relevant documentation snippets from Langchain, Llama Index, and OpenAI official documentation.-
- AlicenseAqualityDmaintenanceA flexible Model Context Protocol server that makes documentation or codebases searchable by AI assistants, allowing users to chat with code or docs by simply pointing to a git repository or folder.11789MIT
TDQS
Scored across 23 tools
The tool set mixes documentation search tools (get_docs, semantic_search, filtered_search) with security scanning (scan_library_vulnerabilities, multiple snyk tools) and other utilities (manage_dev_environment, generate_project_starter), causing confusion. Several search tools have overlapping purposes, and multiple security tools differ only in target (library vs. project, Snyk vs. OSINT).
Tool names use inconsistent patterns: some are verb_noun (clear_cache, get_docs), others are adjective_noun (semantic_search, filtered_search) or brand-specific (snyk_scan_library). While all use underscores, the lack of a consistent verb style harms predictability.
23 tools is excessive for a 'Documentation Search' server. Many tools (e.g., manage_dev_environment, snyk_monitor_project, generate_project_starter) are unrelated to the primary purpose, making the surface feel bloated and unfocused.
For documentation search, the server covers search, filtering, semantic search, examples, and learning paths, but it lacks update or CRUD operations. The inclusion of many security and utility tools suggests the surface is not well-scoped for its stated name, leaving gaps in documentation coverage and adding irrelevant functions.