neutrinos-mcp
Related Servers
Alternatives to neutrinos-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables traceable, version-aware question answering over product documentation, combining vector and graph retrieval to return cited evidence and support agentic workflows.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to search Nokia product documentation with hybrid BM25+vector search and return section-precise deep-link citations.-
- AlicenseAqualityAmaintenanceEnables evidence-based retrieval across official BMC Helix product documentation and isolated private project knowledge, with product, version, project, source, and section provenance. Supports version-aware multi-product indexing, hybrid lexical and optional semantic search, and read-only access to local evidence without touching live Helix systems.9MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve Microsoft AutoGen documentation across versions with smart search and fallback.7 npm1MIT
- AlicenseAqualityBmaintenanceEnables LLM hosts to perform grounded, cited retrieval and answer generation over your own documents using hybrid BM25 and dense search, with explicit refusal when answers are not supported by the sources.510 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides local technical documentation with hybrid search (semantic + BM25) for AI agents, ensuring access to up-to-date framework docs.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct stage of documentation interaction: discover products, search, fetch content, navigate page relationships, compare versions, and explore the knowledge graph. The only mild overlap is between list_related and traverse_knowledge_graph, but the descriptions clarify page-level navigation versus entity-level thematic exploration.
Tool names follow a consistent imperative snake_case pattern, mostly verb_noun (search_docs, fetch_document, list_products, compare_versions, traverse_knowledge_graph). Minor deviations include list_related lacking an explicit object and search_docs/fetch_document mixing plural and singular noun forms.
Six tools is well-scoped for a documentation knowledge server; each tool covers a distinct need without redundancy. The set is neither sparse nor bloated, and every tool earns its place in the workflow.
The surface covers the full read-oriented documentation workflow: product discovery, search, content retrieval, navigation, cross-version comparison, and conceptual graph exploration. For a read-only documentation MCP, there are no obvious dead ends or missing operations.