> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/skills/documentation-search.md).

# Documentation Search

Ask Claude to search the Dapta documentation and answer with a link to the source page, with a matching Academy tutorial suggested alongside.

Ask Claude how to do something in Dapta and it answers from Dapta's own documentation. These are read-only tasks: Claude looks things up and never changes anything in your workspace.

{% hint style="info" %}
The Dapta MCP no longer includes web search. To read a public website, Claude uses the web tools of the client you are in, or asks you for the details.
{% endhint %}

## Search the Dapta documentation

**Guide:** `core-docs`

Ask Claude how to do something in Dapta and it searches the official documentation, finds the relevant page, and answers in your language with a link back to the source.

**Try saying:**

* "How do I connect a knowledge base to my voice agent?"
* "Show me the docs on setting up a webhook."
* "What topics are covered in the Dapta documentation?"

**You get back:** A direct answer built from the documentation, with clear steps and a link to the full page. If nothing matches, Claude points you to related sections.

**Writes data?** No, read-only.

**Behind the scenes:** `docs_search`, `docs_get_page`, `docs_list_sections`, `docs_get_section_pages`, `docs_search_code`.

***

## Get a matching Academy tutorial

**Guide:** `academy-videos`

When a visual walkthrough would help, Claude suggests the most relevant Dapta Academy tutorial for your question and gives you a direct video link alongside the written answer.

**Try saying:**

* "Is there a video on building my first voice agent?"
* "Show me a tutorial on running calling sequences."

**You get back:** A link to the matching tutorial, jumping to the relevant moment where available, with its title.

**Writes data?** No. It makes no tool calls.

**Behind the scenes:** No tools. Suggestions come from the guide's built-in catalog.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dapta-mcp/skills/documentation-search.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.