A Model Context Protocol (MCP) server that provides tools to interact with the [Dash](https://kapeli.com/dash) documentation browser API.
Most browser automation work still happens through a UI a human drives. Dash MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server that provides tools to interact with the Dash documentation browser API.
The Dash MCP server provides tools for accessing and searching documentation directly from Dash, the macOS documentation browser. MCP clients can:
The server publishes 1 tool. What each one is for:
Notice — The Notice tool exposed by this serverSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dash's toolset — Notice — is a fair guide to whether it matches your workflow. It is maintained by kapeli; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Notice | The Notice tool exposed by this server. |
#### in `claude_desktop_config.json`
```json
{
"mcpServers": {
"dash-api": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/Kapeli/dash-mcp-server.git",
"dash-mcp-server"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.