About doc-scraper
doc-scraper is a Go crawler for turning technical documentation into local Markdown corpora. It serves the stored docs to coding agents for offline search, reading, and change tracking.
Key features
- 01Concurrent, resumable documentation crawls
- 02Detection for 30+ documentation generators
- 03Markdown pages with indexing files
- 04Offline BM25 search and page reading
- 05Incremental crawls, watch mode, and diffs
Use cases
- 01Searching technical docs without network access
- 02Reading documentation from a local corpus
- 03Tracking changes between documentation crawls
MCP support
Its MCP server exposes tools for searching and reading stored documentation, checking freshness, and comparing crawls. Coding agents can connect over stdio.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMELLM Documentation Scraper (doc-scraper)
A configurable, concurrent, and resumable web crawler written in Go. Specifically designed to scrape technical documentation websites, extract core content, convert it cleanly to Markdown format suitable for ingestion by Large Language Models (LLMs), and save the results locally.

doc-scraper crawls documentation sites into clean Markdown and serves them to coding agents over MCP. Your agent searches and reads the docs you chose, offline, instead of guessing from training data or a live web search. Point doc-scraper add at any docs page and it detects the framework (30+ docs generators, including Docusaurus, Starlight, Sphinx, VitePress, Material for MkDocs, and mdBook), validates the content selector, and drafts the config for you.
Documentation: https://sriram-pr.github.io/doc-scraper/
Features
- Offline search for agents: BM25 full-text search (
search_docs) and page reads (read_page) over the stored corpus, with no network access - Framework detection: 30+ docs generators recognized, each selector validated on the page, Readability fallback, JavaScript-only shells reported instead of crawled empty
- Clean output: GitHub-Flavored Markdown per page with frontmatter, plus
pages.jsonl,llms.txt, andllms-full.txt - Polite and resumable: robots.txt and sitemaps, per-host rate limits, retries with backoff, resumable crawls, and staged output that never clobbers the last good copy
- Stays fresh: incremental re-crawls, watch mode, and crawl history (
get_freshness,diff_crawl) - Many sites at once: parallel crawls with shared limits
Install
Download a release binary (Linux, macOS, Windows; amd64 and arm64) from the Releases page, or:
go install github.com/Sriram-PR/doc-scraper/v2/cmd/doc-scraper@latest
docker run --rm --user "$(id -u):$(id -g)" -v "$PWD":/data ghcr.io/sriram-pr/doc-scraper:latest crawl -site rust_cli_book
Claude Desktop users can install doc-scraper.mcpb from the latest release instead. Details: Install.
Quick start
doc-scraper add -site rust_cli_book https://rust-cli.github.io/book/index.html # detect, preview, confirm
doc-scraper crawl -site rust_cli_book # Markdown lands in ./crawled_docs/rust_cli_book/
doc-scraper search -site rust_cli_book "error handling"
Then give it to Claude Code:
claude mcp add --transport stdio doc-scraper -- /path/to/doc-scraper mcp-server -config /path/to/config.yaml
See Claude Code setup for scopes and a first prompt.
Docs
- Getting started: install, quick start, adding a site
- Use with agents (MCP): Claude Code, Claude Desktop, any stdio client, and the 13 tools
- Docs frameworks: how detection works, with guides for Docusaurus, Starlight, Sphinx, VitePress, Material for MkDocs, and mdBook
- Configuration and CLI reference
- Detection benchmark
Contributing
Contributions are welcome. Read CONTRIBUTING.md before starting: it covers setup, the testing rules CI enforces, how to claim an issue, and the policy on AI-assisted contributions. Issues labeled good first issue are a good place to begin.
Report security problems privately as described in SECURITY.md. Everyone taking part follows the Code of Conduct.
Privacy Policy
doc-scraper collects nothing: no telemetry, no analytics, no accounts. All output and state stays on your machine, and the only network requests it makes are the crawls and fetches you explicitly ask for. Full policy: PRIVACY.md.
License
This project is licensed under the Apache-2.0 License.
Acknowledgements
- GoQuery for HTML parsing
- html-to-markdown for conversion
- BadgerDB for state persistence
- mcp-go for MCP server implementation
- go-readability for content extraction fallback
- modernc.org/sqlite for the pure-Go crawl-history index
- robotstxt for
robots.txtparsing - yaml.v3 for configuration parsing
- google/uuid for crawl job IDs
- x/sync for the weighted semaphores that cap concurrency
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.