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

# Public help MCP

Distro offers a public, read-only help MCP endpoint for its maintained help-guide summaries.

```
POST /mcp/help
```

Use your Distro application base URL and a compatible HTTP MCP client. No workspace authorization is required for this public help endpoint.

## Available tools

* `help_list` lists maintained guide IDs and titles.
* `help_search` takes a `query` and returns matching guide summaries and source links.
* `help_read` takes an `id` from the list/search and returns that maintained guide text.

## Understand the coverage

This server contains a curated set of guide summaries. It is not a live index of every page in this GitBook site and does not automatically gain every newly published article.

Follow the returned source links or use GitBook search to read a full article. Prefer the current product guide when a brief curated summary omits a new detail.

## Keep help and workspace access separate

Public help can explain how the product works. It cannot read your records, inspect your bookings or apply changes.

Use [Distro MCP](/developers/mcp.md) for authorized workspace operations. Do not give a public help tool private tokens or prospect information merely to ask a general setup question.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.distro.so/developers/help-mcp.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 `build a script that syncs our docs to a CMS` 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.