NiiVue MCP Server
Related Servers
Alternatives to NiiVue MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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.203 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides LLMs with code and documentation search over nautilus_trader via LSP-based symbol lookup and semantic embedding-based doc retrieval.2-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to query locally indexed notes, docs, chat logs, and other files via hybrid vector/BM25 retrieval with section-level citations. Exposes tools, resources, and prompts for searching and asking over the indexed content.-
- FlicenseNot gradedqualityAmaintenanceEnables AI hosts and agents to search, ask, and retrieve cited sections from a locally indexed collection of notes, documents, PDFs, web pages, org files, and chat logs using hybrid vector and BM25 retrieval.-
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.