mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install and configure mcp-docs

Check the install and the collection, connect your agent, search the documentation and read one page.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Four steps from install to your first cited answer.

MCP Docs is an MCP tool: you check it is installed, point your agent at it, and then ask in plain language. Local use needs no network, no token and no root access.

  1. Illustrative
    Check the version and the collection
    $ mcp-docs version
    mcp-docs <version>
    $ mcp-docs cli info
    mcp-docs <version>
    Content source: embedded
    Documents: <N>
    user: <N>
    Step 1 of 4

    Check the install and the collection

    The MAIT image ships mcp-docs and updates it with the image. Run the two read-only checks. A nonzero user: count means the collection is usable; zero means this installation has no usable collection and you should install a published release.

    What you get

    The program answers, and the collection reports its pages as embedded, so lookups need no network.

  2. mcpServers entry
    {
  "mcpServers": {
    "docs": {
      "command": "/usr/local/bin/mcp-docs",
      "args": ["serve"]
    }
  }
}
    Step 2 of 4

    Connect it to your agent

    Any client that accepts an mcpServers launch entry uses this shape. Place it where your client keeps server configuration and restart the client.

    The image installs the program but does not add this entry for you. To reach the documentation from claude.ai or another machine, use the channel endpoint instead: create a docs access token under Account → Access Tokens in your portal account, then add https://<host>/mcp/documentation with the header Authorization: Bearer <token>. Keep the token in user-level client settings, never in a repository. If you reach your tools through the registry, add docs once with mcp_registry_add and the tools carry the docs__ prefix (registry guide).

    What you get

    A client that starts the service on its own, and an agent that can call docs_search, docs_list and docs_read.

  3. Illustrative conversation
    YouHow do I give my agent a docs access token?
    Tool calldocs_search { "query": "give my agent a docs access token", "limit": 3 }
    What happensUp to three candidate pages, each with a path, a score and a short snippet. Select a page relevant to authentication.
    AgentThe authentication page looks like the one. A snippet can leave out a step, so I will read the whole page before I answer.
    Step 3 of 4

    Search

    Ask your agent a question in plain language. It searches with a task-shaped query and gets back candidate pages, each with a path, a score and a snippet. Every path starts with user/.

    What you get

    A short list of pages to read, ranked for this one question. A score is only a ranking, not a confidence percentage.

  4. Illustrative conversation
    YouGo ahead.
    Tool calldocs_read { "path": "user/modules/mcp-docs/authentication.md" }
    What happensThe full Markdown of the authentication page comes back.
    AgentYou copy the token once from Account, Access Tokens in the portal and send it as the Authorization header. I read this from user/modules/mcp-docs/authentication.md.
    Step 4 of 4

    Read one page

    The agent reads the best page in full and answers from it.

    What you get

    An answer taken from a page you can open, with the page named.

Result

An agent that looks things up and says where.

Your agent can search and read the user documentation and cite the exact page it used. The collection is fixed to the release you run, so it changes only when you install a new one.

Next

Where to go next.