Your agent reads the documentation instead of guessing.
MCP Docs lets your agent look things up in the MAIT user documentation instead of answering from memory. It can search the pages, list what exists and read one page in full. The whole collection is built into the application, so there is no website to reach, no search service to run and no copy of the code to find. Ask how to set something up and the agent finds the page, reads it and answers from it, naming the page it used.
It is a lookup, nothing more. It does not browse the internet, write anything or make up answers: it returns pages and pointers to pages, and the agent decides what to do with them.
What you gain over an agent that answers from memory.
Asked about a step it has never seen, an agent guesses, and you find out when it fails. A fixed collection that belongs to the version you run turns the guess into a lookup you can check.
Answers from a page
You can open the page it used and check the answer yourself
- Typical alternative
- The agent answers from memory and gets a step wrong
- Here
- The agent searches, reads the full page and names it in the answer
Matches the version you run
The answer does not drift under you
- Typical alternative
- A live site that moves with unfinished edits
- Here
- The documentation stays fixed until you install a new release, so the available pages stay fixed
Works with no network
Nothing to host, sign in to or keep online, and no copy of the code to find
- Typical alternative
- A hosted site or a search service the agent has to reach
- Here
- The pages are built into the application
Cheap to ask
The conversation carries one page, not the manual
- Typical alternative
- Pasting pages or a whole manual into the conversation
- Here
- The agent gets short snippets first and reads only the page it needs
User documentation only
The agent quotes only the included user documentation
- Typical alternative
- A search over everything nearby
- Here
- Only the user documentation is served; other paths return an error
Two ways in
Pick the route that fits the client, from a terminal agent to claude.ai
- Typical alternative
- One access path that suits only some clients
- Here
- Use it on the same machine with no sign-in, or over the web with an access token from your portal account
Ready in the image, one entry to add.
MCP Docs comes in the MAIT image and updates with it (mait-image). The image installs the program but does not add it to your agent's configuration, so you add one entry. Local use needs no token and no network.
For an agent on another machine, or in claude.ai, use the web endpoint instead: copy a docs access token from Account → Access Tokens in your portal account and send it with each request. You can also connect it through MCP Registry, so a single entry reaches all your tool servers. Get started shows both routes.
Where it sits in the MAIT toolkit.
Where to read on.
- Get started, Use cases and Tools