Resources · Claude connector

Claude Dash connectorWhat Claude can do in your Dash account.

The Claude Dash connector exposes 4 tools. 3 read the documentation library already installed in Dash on your Mac, 1 changes a Dash setting (full-text search on a docset), and none is left undescribed. Below: what Claude looks up, the one thing it switches on, and what it needs to run.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can read your Dash library

You keep reference docs for your languages and frameworks in Dash, the offline documentation browser for macOS. With the connector, you stop alt-tabbing to it: you ask Claude a question about an API, it searches the docsets you already downloaded, opens the matching page and answers from that page rather than from memory.

Know what you actually have offline. Before a flight, you ask which docsets are on the machine. list_installed_docsets returns the installed sets, so you see at once whether the Django or PostgreSQL reference made it onto this laptop.

Answer from the real reference. You ask how a Swift method behaves. search_documentation looks across docsets and your saved snippets, then load_documentation_page opens the page the search pointed to. Claude reads that page and quotes what it says.

Make a large docset searchable word by word. When a title search misses, enable_docset_fts turns on full-text search for one docset. That is the only tool here that changes something, and what it changes is a Dash setting, not your files.

What it will not do: it does not download new docsets, edit a page or touch your code. It runs only inside Claude Desktop on a Mac, with Dash 8 installed, and Kapeli calls it a work in progress. Nothing fires on its own either; Claude calls these tools while it answers you. For how other connectors handle account data, see the Claude airtable connector page.

Vocabulary

The vocabulary in one minute

Five words you will meet while setting up Dash in Claude.

Connector
The link you set up once between Claude and something you already use, so Claude can work with it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs on its own; the directory sheet lists them by name.
Approval
The confirmation Claude waits for before it goes ahead with something that changes a setting or an account, shown in the chat when it matters.
Directory
The official catalogue where every connector has its own sheet: who publishes it, what it is for, and which tools it exposes.
MCP
The shared standard connectors are built on, which is what lets an assistant like Claude talk to an outside app such as Dash.
Connect

Set up Dash in Claude in three steps

  1. 01

    Find Dash in Claude's settings

    In Claude Desktop, open Customize, then Connectors, and look for Dash in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can use it.

  2. 02

    Start the connection from its row

    Launch the setup from the Dash row. If the service shows its own sign-in window, that is where you hand over access. If the link breaks later, use Disconnect and add it again.

  3. 03

    Read what you are granting

    Check the access screen before you confirm. It belongs to the service, not to Claude, and it decides what the access covers. Whatever you grant there can be taken back the same way.

Tools

The 4 tools, sorted by what they do

Dash gives Claude 4 tools: 3 that read your account, 1 that change something in it.

Two groups: what Claude reads in your library, and the one setting it can change. The names stay exactly as Claude shows them.

  • 3 read
  • 1 write

What Claude reads (3)

3 tools

Three tools that look through your installed docsets without changing them.

list_installed_docsets

Returns every documentation set installed in your copy of Dash, so Claude knows which references it can search before it starts looking.

When it helps
you are about to work offline and want to confirm the React and Node.js docs are already on the machine.
Watch out
it only sees what is installed; a docset you never downloaded simply is not in the answer.

Sourcegithub.com · September 30, 2026 ↗

search_documentation

Runs one query across your docsets and your saved code snippets, and hands Claude a list of matching entries it can open next.

When it helps
you half remember a Python function name and want the exact entry, plus the snippet you stored for it last year.
Watch out
if a term buried in a page does not come up, enable_docset_fts is the tool Kapeli provides for full-text search.

Sourcegithub.com · September 30, 2026 ↗

load_documentation_page

Opens the full page behind a search result, using the link the search step returned, so Claude answers from the text of the reference itself.

When it helps
you want the parameters and return value of a Go function spelled out, not a summary from memory.
Watch out
it works from a search result, so a lookup always starts with search_documentation.

Sourcegithub.com · September 30, 2026 ↗

What Claude changes (1)

1 tool

One tool that flips a Dash setting. No source describes a confirmation specific to it, so the general approval rule below applies.

enable_docset_fts

Approval: see the rule

Turns on full-text search for one docset you name. From then on, searches in that docset match words inside pages, not only titles.

What Claude asks for
no source describes a confirmation for this tool, so the general approval rule below is what covers it.
When it helps
your Rust searches keep missing a term that you know appears somewhere in the text.
Watch out
it changes a setting inside Dash for that docset, not only for this chat.

Sourcegithub.com · September 30, 2026 ↗

Approvals

What Claude asks before it acts

By default, Claude stops and asks you before any action it takes on your behalf. The request shows up in the chat, at the moment it matters.

On a Team or Enterprise workspace, the owners decide whether members can let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keep reading open and close anything that changes data. That setting applies to everyone and nobody overrides it from their own account. Claude also works with your access and nothing more: a docset that is not in your Dash stays out of reach.

Plans

Which plans include it

None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere; that is a real gap in the catalogue, not something we missed.

The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. For the current status, check the Dash sheet in the official directory. Everything above comes from Kapeli alone: Anthropic has no page of its own for this connector.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you; nothing runs when a docset updates or a new one lands.

The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Install what comes from a publisher you trust, here Kapeli itself. To browse other connector pages, start from the Integrations hub.

Need help

Need help connecting Dash to Claude?

A person reads every message.

FAQ

Frequently asked questions about the Claude Dash connector

01What can Claude do with the Dash connector?
Claude can look through the documentation you already keep in Dash and answer from it. Three of its four tools list your installed docsets, search across docsets and saved snippets, and open the full page behind a search result. The fourth switches on full-text search for a docset you name. All four are described by Kapeli, the publisher, so none of them is a mystery. In practice, you ask a question about an API and Claude does the looking up for you, in the docsets on your own Mac, without you switching windows.
02Can Claude change anything in Dash?
Yes, but only one thing: it can turn on full-text search for a specific docset. That is a Dash setting, and it stays on after the chat ends. The other three tools only read. By default the sheet exposes nothing that edits pages, deletes docsets or touches your code, though an administrator could open more on a workspace. If your workspace owner has limited the connector to reading, even that one setting change is off the table for you.
03Does Claude ask before it changes a Dash setting?
By default, Claude asks for confirmation before any action it takes on your behalf. No source describes a confirmation specific to the full-text search tool, so that default rule is what applies. On a Team or Enterprise workspace, owners decide whether members may let some actions through without a prompt, and they can block that tool for everyone. In short, expect the same default prompt you would get for any change made on your behalf.
04Which Claude plans include the Dash connector?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The published rule says remote connectors are open to all users, and desktop extensions like Dash install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector first. For the current status, check the Dash sheet in the directory. The directory sheet is the only place that shows the current status, and it can change from one update of the catalogue to the next.
05Can Claude see everything on my Mac through Dash?
No. Claude works with your access and nothing more, and this connector only reaches the documentation library inside Dash. It lists and searches the docsets you installed, plus your snippets, and opens pages from them. Files elsewhere on the machine and your projects are not part of what the publisher describes. If a docset is not installed in Dash, Claude cannot search it, and it cannot download it for you either.
06Why does the Dash connector not work on my computer?
The most likely reason is the setup, not Claude. Kapeli requires macOS and Dash 8, and the directory lists the connector as a local extension for Claude Desktop only. On Windows, on an older Dash, or in Claude on the web, the tools have nothing to connect to. Updating Dash is the first thing to check. Kapeli also calls the connector a work in progress, so a behaviour that changes after an update is not unusual.
07Should I use Claude or an automation tool with Dash?
They do different jobs, so it depends on the use. Claude with this connector helps while you work: you ask a question, it looks up the reference and answers. An automation tool runs steps on its own when something happens, and this connector never starts anything by itself. For reading documentation in the flow of a question, the connector is the fit. The two can sit side by side: one for questions during the day, the other for jobs that run on a schedule.