Dash Mcp Server
Search Apple Dash docsets from your agent so API answers cite the same offline docs you already use on macOS.
Overview
io.github.Kapeli/dash-mcp-server is a Build-phase MCP server that lets agents search 200+ Dash docsets on macOS for API and framework documentation.
What is this MCP server?
- MCP bridge to Dash, the macOS API documentation browser
- Search across 200+ docsets from the agent
- Stdio transport PyPI package dash-mcp-server v1.1.1
- Keeps documentation discovery inside the agent workflow on Mac
- Version 1.1.1 on PyPI identifier dash-mcp-server
- Search 200+ docsets
What problem does it solve?
Agents guess at SDK APIs when they cannot see the exact docset pages you trust in Dash.
Who is it for?
Mac-based solo developers who own Dash and want agent answers grounded in installed Apple, language, and framework docsets.
Skip if: Windows or Linux-only setups without Dash, or teams that standardize purely on web-hosted docs.
What do I get? / Deliverables
After install, your agent can query Dash docsets over MCP so implementation help aligns with offline reference you already maintain.
- Agent-callable Dash docset search results
- Faster API verification against 200+ docsets
- Reduced manual context switch to the Dash UI
Recommended MCP Servers
Journey fit
How it compares
Dash docset search MCP integration, not a generic web browser automation skill.
Common Questions / FAQ
Who is io.github.Kapeli/dash-mcp-server for?
It is for macOS developers who use Dash daily and want Claude Code, Cursor, or similar agents to search those docsets directly.
When should I use io.github.Kapeli/dash-mcp-server?
Use it while implementing features when you need version-accurate API lookups without leaving the agent thread.
How do I add io.github.Kapeli/dash-mcp-server to my agent?
Install Dash on macOS, install the PyPI dash-mcp-server package, add a stdio MCP server entry in your client config pointing at the published command, then reload MCP tools.