doc-scraper
Related Servers
Alternatives to doc-scraper
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.3020AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceA documentation MCP server that crawls websites and Git repositories, stores them as Markdown, and provides tools to search and retrieve documentation for local LLMs and AI agents.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceDocumentation crawler MCP server that crawls and indexes documentation sites so that any MCP-compatible AI can search, read, and expand on the content.1-
- AlicenseAqualityCmaintenanceLocal-first MCP server providing semantic search over library docs, fully offline. Single Go binary speaks MCP over stdio against a vector index pinned to the binary version. Like Context7 with the internet turned off. Apache 2.0. Linux + macOS, also available as a container image.24Apache 2.0
- AlicenseAqualityBmaintenanceGo MCP server for multi-format document access — PDF, TXT, MD, DOCX, CSV, images. 12 tools including OCR, search, table extraction, and URL fetch. Single binary, no runtime.1311MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for crawling web documentation and storing it in a Supabase vector database.-
TDQS
Scored across 13 tools
Most tools target clearly distinct operations (crawl lifecycle, page access, site config, search). A few boundaries blur: get_freshness vs describe_server vs get_job_status all surface crawl/job state, and get_page vs read_page are only separable by carefully reading the descriptions. The descriptions do explicitly call out these distinctions, which mitigates the overlap.
Every tool is snake_case verb_noun (crawl_site, get_job_status, read_page, save_site, search_docs), with only the conventional noun-only list_sites/list_pages as natural exceptions. No mixed conventions or camelCase.
13 tools sits comfortably in the well-scoped range, and each maps to a real workflow step (crawl, wait, inspect, diff, search, read, configure). Nothing appears redundant or padding.
The crawl lifecycle, search, page reads, and site onboarding are all covered, including diff and cancellation. The main gap is site lifecycle management: there is no delete_site/remove_site and no explicit update beyond overwriting via save_site with replace:true, so removing a configured site is a dead end.