DocsetMCP MCP Server

Model Context Protocol server for Dash-style docsets

Local serverstdioPython

What is the DocsetMCP MCP server?

Model Context Protocol server for Dash-style docsets. That is what the docsetmcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

DocsetMCP is a Model Context Protocol (MCP) server that seamlessly integrates your local Dash docsets with AI assistants like Claude, enabling instant access to offline documentation without leaving your conversation.

  • 📚 Instant Documentation: No switching, no web searches. Get straight to the docs directly in your AI conversation
  • 🔒 Local and Private: Work with docset files on your machine
  • Lightning Fast: Optimized caching and direct database queries
  • 🎯 Precise Results: Get exactly what you need with smart filtering

Getting it running

docsetmcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Testing — The Testing tool exposed by this server

What it needs from you

Configuration is passed through the environment: DOCSET_PATH, CHEATSHEET_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • macOS (Dash is Mac-only) - Dash with desired docsets downloaded - Python 3.10 or higher - UV package manager (How to Install) - An AI assistant that supports MCP (Claude Desktop, Claude Code CLI, Cursor IDE, etc.)

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. DocsetMCP's toolset — Testing — is a fair guide to whether it matches your workflow. It is maintained by codybrom; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
TestingThe Testing tool exposed by this server.

How to install the DocsetMCP MCP server

{
  "mcpServers": {
    "docsetmcp": {
      "command": "uvx",
      "args": ["docsetmcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • macOS (Dash is Mac-only) - Dash with desired docsets downloaded - Python 3.10 or higher - UV package manager (How to Install) - An AI assistant that supports MCP (Claude Desktop, Claude Code CLI, Cursor IDE, etc.)
VariableDescriptionRequired
DOCSET_PATHFilesystem location the server is allowed to use.Optional
CHEATSHEET_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use DocsetMCP to Testing.

Frequently asked questions

It connects DocsetMCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Testing) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with DocsetMCP directly.