Skip to main content
Glama

mcp-server-dash

A Model Context Protocol (MCP) server that provides tools to interact with the Dash documentation browser API.

Dash 8 is required. You can download Dash 8 at https://blog.kapeli.com/dash-8.

mcp-name: io.github.Kapeli/dash-mcp-server

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

Notice

This is a work in progress. Any suggestions are welcome!

Related MCP server: dash-mcp-server-node

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 installed

  • Python 3.12 or higher

  • uv

Configuration

Using uvx

brew install uv

in claude_desktop_config.json

{
  "mcpServers": {
      "dash-api": {
          "command": "uvx",
          "args": [
              "--from",
              "git+https://github.com/Kapeli/dash-mcp-server.git",
              "dash-mcp-server"
          ]
      }
  }
}

in Claude Code

claude mcp add dash-api -- uvx --from "git+https://github.com/Kapeli/dash-mcp-server.git" "dash-mcp-server"

Available Tools

4 tools
enable_docset_ftsB
Enable full-text search for a specific docset.

Args:
    identifier: The docset identifier (from list_installed_docsets)

Returns:
    True if FTS was successfully enabled, False otherwise

Inputs: identifier (required). Returns: result

list_installed_docsetsA

List all installed documentation sets in Dash. An empty list is returned if the user has no docsets installed. Results are automatically truncated if they would exceed 25,000 tokens.

Inputs: no named parameters. Returns: Result from listing docsets.

load_documentation_pageA
Load a documentation page from a load_url returned by search_documentation.

Args:
    load_url: The load_url value from a search result (must point to the local Dash API at 127.0.0.1)

Returns:
    The documentation page content as plain text with markdown-style links

Inputs: load_url (required). Returns: Documentation page content.

search_documentationA
Search for documentation across docset identifiers and snippets.

Args:
    query: The search query string
    docset_identifiers: Comma-separated list of docset identifiers to search in (from list_installed_docsets)
    search_snippets: Whether to include snippets in search results
    max_results: Maximum number of results to return (1-1000)

Results are automatically truncated if they would exceed 25,000 tokens.

Inputs: query (required), docset_identifiers (required), search_snippets, max_results. Returns: Result from searching documentation.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. enable_docset_fts configures search capabilities, list_installed_docsets enumerates available resources, search_documentation finds content, and load_documentation_page retrieves specific pages. The boundaries between these operations are well-defined and unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with clear, descriptive action-object pairs. The naming convention is uniform throughout: enable_docset_fts, list_installed_docsets, load_documentation_page, and search_documentation all maintain the same structure and style.

    Tool Count4/5

    Four tools is reasonable for a documentation search server, covering core operations of listing, searching, and viewing documentation. While this is a minimal but functional set, it could potentially benefit from additional utilities like docset management or search refinement tools, but the current count is appropriate for the basic scope.

    Completeness4/5

    The toolset provides complete coverage for the core documentation search workflow: discovering available docsets, enabling search features, searching across documentation, and loading specific pages. The only minor gap is the absence of docset installation/removal tools, but the server appears focused on search operations rather than full docset management.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      10
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and managing a documentation index, including searching libraries, resolving versions, indexing from URLs or local files, refreshing content, and removing entries.
      MIT