NiiVue MCP Server
Related Servers
Alternatives to NiiVue MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides local technical documentation with hybrid search (semantic + BM25) for AI agents, ensuring access to up-to-date framework docs.MIT
- AlicenseNot gradedqualityAmaintenanceProvides a hybrid search engine for Obsidian vaults, enabling LLM agents to query notes with BM25 keyword and vector semantic search, metadata filtering, and sibling-document retrieval.5 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides LLMs with code and documentation search over nautilus_trader via LSP-based symbol lookup and semantic embedding-based doc retrieval.2-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve information from large technical documentation (OpenAPI specs, markdown) via intelligent chunking and semantic search.MIT
- AlicenseAqualityDmaintenanceProvides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.76 npm1MIT
- FlicenseAqualityCmaintenanceEnables LLM agents to search and retrieve a hybrid knowledge base of manuals, videos, PDFs, DOCX files and images through tools for hybrid BM25-plus-vector search with facet and tag filters, full document retrieval, semantically similar document lookup, and timestamped video transcript segments. It ships with an in-memory backend for instant local use and an identical Elasticsearch backend for production deployment over stdio or authenticated HTTP.5-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity: get_niivue_api fetches API method details, get_niivue_doc fetches doc page content, get_niivue_overview returns the overview, list_niivue_docs lists docs, search_niivue_api searches API methods, and search_niivue_docs searches documentation. The tools are well-differentiated by their target resource (API vs. docs) and action (get vs. list vs. search).
All tool names follow a consistent verb_noun pattern with 'niivue' as a prefix, using snake_case throughout. The verbs (get, list, search) are applied predictably to the nouns (api, doc, overview, docs), making the naming highly consistent and readable.
With 6 tools, the server is well-scoped for its purpose of accessing Niivue documentation and API information. Each tool earns its place by covering distinct aspects like fetching, listing, and searching, without being too sparse or bloated, which is ideal for a documentation-focused server.
The tool set provides comprehensive coverage for accessing and searching Niivue documentation and API details, with no obvious gaps for the stated purpose. Minor gaps might include lack of update or delete operations, but these are not expected in a read-only documentation context, so the surface is nearly complete.