LabscoMCP early access ↗
ZebraRoyMCP SERVER

Read Docs MCP

Turn a git repository's docs folder into tools an assistant can list, read and search. Without a repository, it explains how to lay that folder out.

by ZebraRoy ↗Prompts, Skills & Instruction PacksCommunity

LABSCO SUMMARY

It reads documentation you have structured for it. It does not write that documentation.

Pointed at a repository, it clones it and builds tools from the docs folder, so the assistant reads your library's own documentation instead of guessing. That folder follows a set layout, a read-docs-mcp.json plus one folder per module, and run without a repository the server returns the instructions for building it.

What it is

A documentation reader for one git repository. Started with --name and --git-repo-path, it clones the repository and generates tools from its docs folder; started without them, it offers one tool that explains the folder layout it expects.

What you get

  • Tools prefixed with your --name that list, overview and read the items in each docs module, plus a fuzzy search across the documentation files.

Requirements

Nothing — no account, no key.

Setup effort

One command — npx -y read-docs-mcp --name=<YOUR_LIBRARY_NAME> --git-repo-path=<YOUR_GIT_REPO_PATH>