Reported issues for WebReaper

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to WebReaper.

Most discussed

MCP HTTP host: release plumbing (CANDIDATES + container image)

Parent

#239

What to build

Release plumbing for the new package and its container image. Add WebReaper.Mcp.AspNetCore to the release CANDIDATES list so it versions in lockstep with the other packages, and publish a versioned container image as part of the release. This slice is HITL: it needs a human decision on the container registry (GHCR vs Docker Hub), the image name and tag scheme, and the credentials, and it touches the release workflow.

Acceptance criteria

• `WebReaper.M

Read the thread · 2026-06-04 · closed · 0 comments

MCP HTTP host: Chromium-baked Docker image + compose sidecar + n8n quickstart

Parent

#239

What to build

A Chromium-baked Docker image for the HTTP host, a docker-compose example, and an n8n quickstart. The image bundles a managed Chromium so browser=true works out of the box (modeled on the existing playground Tier-B lean image). The compose example shows the server next to n8n, with an optional browserless sidecar wired via WEBREAPER_CDP_URL. The n8n quickstart documents pointing the MCP Client node at the server URL with a bearer token over Streamable HTTP.

Read the thread · 2026-06-04 · closed · 0 comments

MCP: per-call model override on extract_with_prompt + LLM config validation

Parent

#239

What to build

A per-call model override on extract_with_prompt, plus validation of the LLM configuration. The tool gains an optional model parameter so a workflow can vary the model per call; the API key stays environment-only (the ADR-0084 OpenAI-compatible client), never a tool parameter. The config module is extended to read and validate the WEBREAPER_LLM_* set, and an LLM tool called without that configuration fails with an actionable error rather than a silent or

Read the thread · 2026-06-04 · closed · 0 comments

MCP: WEBREAPER_CDP_URL browser-transport selection + concurrency cap (shared)

Parent

#239

What to build

Browser-transport selection in the shared WebReaper.Mcp, so browser=true calls either launch managed Chromium or connect to an external CDP endpoint. A pure decision keyed on the browser flag and WEBREAPER_CDP_URL yields one of NoBrowser, LaunchManagedChromium, or ConnectToCdp(url); the tool layer turns that into the page-loader wiring. When WEBREAPER_CDP_URL is set, browser calls connect to that endpoint (a shared browserless pool) instead of launchin

Read the thread · 2026-06-04 · closed · 0 comments

MCP: bounded crawl tool (shared WebReaperTools)

Parent

#239

What to build

A bounded whole-site crawl tool added to the shared WebReaperTools class (so it appears on both the HTTP and stdio hosts). It takes a URL, an optional max_pages, and a browser flag, and performs an on-domain recursive sweep mirroring the CLI crawl command's shape (Crawl(url).Sweep(...) bounded by a page limit), collecting one record per page. The default max_pages is 50 (not the CLI's 1000) with a hard clamp, because MCP has no streaming and an unb

Read the thread · 2026-06-04 · closed · 0 comments

MCP HTTP host: bearer auth + non-loopback bind guard

Parent

#239

What to build

Bearer-token authentication for the HTTP host, plus the configuration module the rest of the feature extends. A request must present a matching bearer token (read from WEBREAPER_MCP_TOKEN) or receive 401. The accept-or-reject logic is a pure decision module the ASP.NET middleware calls. A configuration parser/validator is introduced here: it reads the token and the bind address from the environment into a validated options record, or fails with an actionable e

Read the thread · 2026-06-04 · closed · 0 comments

MCP HTTP host: serve existing tools over Streamable HTTP (WebReaper.Mcp.AspNetCore)

Parent

#239

What to build

A new WebReaper.Mcp.AspNetCore satellite that hosts the existing MCP tools over Streamable HTTP, so URL-based MCP clients (n8n, hosted agents) can reach WebReaper. It references WebReaper.Mcp and reuses the WebReaperTools class verbatim. The host wires the MCP server with the HTTP transport in stateless mode, maps the MCP endpoint at the application root, and exposes a /health endpoint. For this slice the server binds loopback only and has no authent

Read the thread · 2026-06-04 · closed · 0 comments

ADR-0086: WebReaper.Mcp.AspNetCore Streamable HTTP MCP transport (n8n / remote clients)

Design of record: ADR-0086 (PR #238). This PRD operationalizes it. Related: ADR-0049 (MCP satellite, stdio), ADR-0073 (MCP bakes Cdp), ADR-0083 (escalating page loader), ADR-0084 (WebReaper.AI.Http client + WEBREAPER_LLM_*), ADR-0085 (climb-progress observer).

Problem Statement

I run n8n and want to call WebReaper's scrape / map / extract tools from my workflows. WebReaper ships an MC

Read the thread · 2026-06-04 · open · 0 comments

Most recent

docs: surface .Subscribe as the in-process result-collection idiom

Parent

#233

What to build

Make WebReaper's existing in-process result-collection idiom, ScraperEngineBuilder.Subscribe(Action<ParsedData>) (ADR-0038), discoverable, so consumers stop hand-rolling a custom IScraperSink just to get records back in their own process. Three doc touch-points, all the same theme, shipped together:

1. README: add a short "get records in-process" recipe under "API overview" (sibling to "Persist progress locally" and "Authorization"). Show collecting into a

Read the thread · 2026-06-03 · closed · 0 comments

The remaining reports are on the project's issue tracker.