Three tools for reading MAIT documentation.
MCP Docs gives your agent three tools to search, list and read the MAIT user documentation. All three only read.
A successful result arrives as JSON text inside a content block, so the agent decodes it before it reads the fields.
Search, list and read.
| Tool | Use it to | Parameters |
|---|---|---|
docs_search | Find pages when you know the problem but not the page name, using words from your question. You get the query and a ranked list of matching pages, best first, each with a score and a short snippet. An empty query returns nothing. | query (required), limit (optional, default 10, from 1 to 100) |
docs_list | Browse page paths without ranking, to see what exists for a component. You get the paths and a count. | prefix (optional, a string such as user/modules/mcp-git) |
docs_read | Read one full page as Markdown. You get the page's path and its content. | path (required, such as user/index.md) |
Why: search finds, list shows what exists, read gives the whole page. A snippet is a pointer, not the page, so an agent reads the page before it acts on it. Equal scores can appear in a different order, so choose by relevance, not by position.
When a call fails, the reason is in the tool error:
| Request | Result |
|---|---|
A user/ path that is in the collection | path and content |
A user/ path that is not in the collection | document not found: <path> |
An unsupported prefix, or a path that contains .. | path must be under user/ and must not contain .. |
Two routes, and which one needs a token.
| Access | Where it runs | Access control |
|---|---|---|
| Local stdio | mcp-docs serve, started by your client | Whoever can start the process |
| Channel HTTPS | https://<host>/mcp/documentation on edge, beta or stable | A docs access token from your portal account on that channel |
On the channel endpoint the token travels as Authorization: Bearer <token>, and the Docs access for your agent feature must be on in Account → Features. A token works on its own channel only. See Authentication for its lifetime, renewal and the supported clients.
What to expect.
| Limit | Value |
|---|---|
| Collection | User documentation only; other paths return an error |
| Freshness | Fixed to the release you run; a new collection arrives with a new release and a restart |
| Writes | None |
| Channel rate | An average of 20 requests per second with bursts of 40 |
On the channel endpoint a request without a valid token is rejected before any tool runs. Only user documentation is served; other paths return an error. See Troubleshooting.