dash-mcp-server-node
Official# mcp-server-dash (Node.js)
A Model Context Protocol (MCP) server that provides tools to interact with the [Dash](https://kapeli.com/dash) documentation browser API.
Dash 8 is required. You can download Dash 8 at https://kapeli.com/dash.
## Overview
The Dash MCP server provides tools for accessing and searching documentation directly from Dash, the macOS documentation browser. MCP clients can:
- List installed docsets
- Search across docsets and code snippets
- Load documentation pages from search results
- Enable full-text search for specific docsets
## Tools
1. **list_installed_docsets**
- Lists all installed documentation sets in Dash
2. **search_documentation**
- Searches across docsets and snippets
3. **load_documentation_page**
- Loads a documentation page from a `load_url` returned by `search_documentation`
4. **enable_docset_fts**
- Enables full-text search for a specific docset
## Requirements
- macOS (required for Dash app)
- [Dash](https://kapeli.com/dash) installed
- Node.js 18 or higher
## Configuration
### Using npx
#### in `claude_desktop_config.json`
```json
{
"mcpServers": {
"dash-api": {
"command": "npx",
"args": [
"-y",
"git+https://github.com/Kapeli/dash-mcp-server-node.git",
"dash-mcp-server"
]
}
}
}
```
#### in `Claude Code`
```bash
claude mcp add dash-api -- npx -y "git+https://github.com/Kapeli/dash-mcp-server-node.git" dash-mcp-server
```
### From source
```bash
git clone https://github.com/Kapeli/dash-mcp-server-node.git
cd dash-mcp-server-node
npm install
npm run build
```
#### in `claude_desktop_config.json`
```json
{
"mcpServers": {
"dash-api": {
"command": "node",
"args": ["/absolute/path/to/dash-mcp-server-node/dist/index.js"]
}
}
}
```
#### in `Claude Code`
```bash
claude mcp add dash-api -- node /absolute/path/to/dash-mcp-server-node/dist/index.js
```
## Development
```bash
npm install
npm run dev # watch mode
npm test # run tests
npm run lint # type check
```
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.