dash-mcp-server-node
OfficialRelated Servers
Alternatives to dash-mcp-server-node
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides tools to interact with the Dash documentation browser API, allowing users to list installed docsets, search across documentation, and enable full-text search.4180MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants with instant access to local Dash documentation docsets and cheatsheets, enabling offline documentation searches across 165+ programming languages, frameworks, and developer tools directly within conversations.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables offline, real-time search of Apple Developer Documentation from Xcode's local index, returning full text, code examples, availability, and framework listings without network calls.MIT
- AlicenseAqualityAmaintenanceProvides fast, token-efficient search over coding agent documentation (e.g., Claude Code, Cursor) using local SQLite FTS5 indexing, with tools for searching snippets, reading pages, and grepping markdown.5MIT
- FlicenseNot gradedqualityBmaintenanceEnables searching and fetching documentation pages from a wide range of programming languages, frameworks, game engines, and tools. Supports multiple sources and returns relevant documentation snippets.1-
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Godot documentation pages using fuzzy search, with support for multiple documentation versions.MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: listing installed docsets, searching documentation, enabling full-text search, and loading a documentation page. There is no meaningful overlap between any pair, so an agent can reliably select the right tool.
All tools follow a consistent snake_case verb_noun pattern: list_installed_docsets, search_documentation, enable_docset_fts, and load_documentation_page. The noun phrases are specific and the naming style is uniform throughout.
Four tools is a compact, well-scoped set for a documentation browsing server. Each tool contributes a necessary part of the workflow with no redundancy or bloat.
The core workflow is covered: list installed docsets, enable full-text search, search across documentation, and load pages. The main missing piece is a paired disable_docset_fts operation, but that is an optional control rather than a blocking gap.