DEV.co
RAG Frameworks · 0xMassi

webclaw

webclaw is a Rust-based web scraper and crawler that extracts clean markdown, JSON, and LLM-ready content from websites. It runs locally via CLI, MCP server, or self-hosted REST API, with optional cloud features for JavaScript-heavy sites and advanced workflows.

Source: GitHub — github.com/0xMassi/webclaw
1.7k
GitHub stars
181
Forks
Rust
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repository0xMassi/webclaw
Owner0xMassi
Primary languageRust
LicenseAGPL-3.0 — OSI-approved
Stars1.7k
Forks181
Open issues0
Latest releasev0.6.14 (2026-06-27)
Last updated2026-07-02
Sourcehttps://github.com/0xMassi/webclaw

What webclaw is

Rust extraction engine with local-first architecture supporting multiple output formats (markdown, JSON, LLM-optimized text, HTML). Integrates via CLI, MCP protocol for AI agents, REST API, and SDKs (TypeScript, Python, Go). Optional cloud backend for bot-protected sites and async jobs.

Quickstart

Get the webclaw source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/0xMassi/webclaw.gitcd webclaw# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

AI Agent Web Access & RAG Pipelines

Provide Claude, Cursor, and other MCP-compatible agents clean, structured page context for real-time research. Crawl documentation, blogs, and knowledge bases to build RAG indexes without noise.

Competitor & Market Intelligence

Monitor pricing pages, changelogs, product pages, and docs. Track changes over time with built-in diff, extract brand assets (logos, colors, fonts), and structure competitive data for analysis.

Structured Data Extraction at Scale

Transform messy web pages into typed JSON for automations. Batch process multiple URLs, apply include/exclude selectors, extract only main content, and integrate extracted data into applications via SDK.

Implementation considerations

  • AGPL-3.0 license requires legal review before use in proprietary commercial products; source-code disclosure obligations apply if modified and distributed.
  • Local extraction works without API key for static HTML; set WEBCLAW_API_KEY for JavaScript rendering, bot-protected sites, and advanced search/research workflows.
  • Build from source requires platform-specific dependencies (libssl-dev, cmake, clang); use Homebrew, prebuilt binaries, or Docker to avoid compilation overhead.
  • MCP integration works with Claude Desktop, Cursor, Windsurf, and other compatible agents; use `npx create-webclaw` for automatic configuration.
  • Extraction quality depends on site structure and bot-detection triggers; test against target sites before production deployment.

When to avoid it — and what to weigh

  • Heavy JavaScript Rendering Required (Without API Key) — Local CLI and MCP server cannot render JavaScript-heavy SPAs without cloud API. Complex modern web apps may return incomplete content unless WEBCLAW_API_KEY is set for hosted rendering.
  • Permissive Commercial License Needed — Licensed under AGPL-3.0, which requires source-code disclosure if modified and distributed. Not suitable for proprietary closed-source commercial products without careful legal review.
  • Minimal or No Operational Overhead Desired — Self-hosting requires Rust build dependencies (pkg-config, libssl-dev, cmake, clang, build-essential) and infrastructure. Managed service at webclaw.io eliminates this but introduces vendor dependency.
  • Guaranteed Crawl Success Against All Sites — Bot detection, Cloudflare, and JavaScript-protected content require hosted API. Local extraction is fast but may encounter blocks; no guarantee of universal site coverage.

License & commercial use

Licensed under AGPL-3.0 (GNU Affero General Public License v3.0). Requires source-code disclosure if modified and distributed as a service or in derivative works. Network use triggers copyleft obligations.

AGPL-3.0 is a strong copyleft license. Using the unmodified OSS version for internal operations (via CLI or self-hosted server) is likely permissible, but distributing modifications, offering as a managed service, or incorporating into proprietary products requires legal review and potential source disclosure. Hosted webclaw.io service may have separate commercial terms; requires review.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityLow
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

Web scraping inherently interacts with untrusted remote content; input validation, output sanitization, and bot-detection evasion (TLS fingerprinting mentioned in topics) carry risk. AGPL-3.0 source is auditable. No security audit, CVE history, or threat model provided. Self-hosted deployments inherit infrastructure security burden; managed service shifts risk to vendor.

Alternatives to consider

Firecrawl

Purpose-built web scraping API with built-in JavaScript rendering, bot handling, and LLM optimization. Proprietary SaaS; mention of 'Firecrawl-alternative' in webclaw topics suggests feature overlap but different licensing model.

Cheerio (Node.js) / BeautifulSoup (Python)

Lightweight, permissive open-source libraries for HTML parsing and extraction. Require manual orchestration; no built-in crawling, JavaScript rendering, or LLM-optimized output, but simpler licensing (MIT/BSD).

Crawl4AI (Python)

Python-native crawler with Markdown/JSON output, LLM integration, and MCP support. Unknown license and maintenance status; different language ecosystem than webclaw's Rust core.

Software development agency

Build on webclaw with DEV.co software developers

webclaw works locally via CLI or MCP for zero-friction integration with Claude, Cursor, and custom apps. Review AGPL-3.0 licensing before production use. Start with the Homebrew or Docker install, or evaluate the hosted API for JavaScript-heavy sites.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

webclaw FAQ

Can I use webclaw locally without an API key?
Yes, the CLI and MCP server extract static HTML content locally without authentication. Set WEBCLAW_API_KEY only if you need JavaScript rendering, bot-protected site access, web search, or async crawl jobs via the hosted API.
What are the AGPL-3.0 license implications for my business?
Using the unmodified CLI or self-hosted server for internal operations is likely permissible. Modifying code, distributing derivatives, or offering it as a service triggers source-code disclosure obligations. Legal review required before commercial deployment.
How do I integrate webclaw with my AI agent?
Use `npx create-webclaw` for automatic MCP configuration with Claude Desktop, Cursor, Windsurf, and other compatible agents. Alternatively, configure the MCP server manually in your agent's config file, or call the REST API via TypeScript/Python/Go SDKs from your application code.
What if a site uses JavaScript heavily?
Local extraction returns incomplete content for JavaScript-heavy SPAs. Set WEBCLAW_API_KEY to enable cloud-based JavaScript rendering via webclaw.io. Test against target sites before relying on extraction.

Custom software development services

Adopting webclaw is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate rag frameworks software in production.

Ready to add web scraping to your AI agent or application?

webclaw works locally via CLI or MCP for zero-friction integration with Claude, Cursor, and custom apps. Review AGPL-3.0 licensing before production use. Start with the Homebrew or Docker install, or evaluate the hosted API for JavaScript-heavy sites.