WebReaper vs Hyperbrowser
A side-by-side look at the WebReaper and Hyperbrowser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose WebReaper for search & data extraction work over a hosted endpoint; choose Hyperbrowser for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose WebReaper when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
WEBREAPER_MCP_TOKEN.
Choose Hyperbrowser when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You want tools like
hyperbrowser_scrape, hyperbrowser_extract, hyperbrowser_crawl.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 56/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | WEBREAPER_MCP_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 152 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View WebReaper | View Hyperbrowser |
Tools & capabilities
WebReaper tools
No tool names declared yet. Check the project README from the listing page.
Hyperbrowser tools 3
hyperbrowser_scrapeScrape a single web page from a cloud browser and return clean content (markdown, html, links, and page metadata). Handles JS-rendered pages. Example: hyperbrowser_scrape({ url: "https://example.com", _apiKey: "your-key" })hyperbrowser_extractExtract structured JSON data from one or more web pages using an LLM. Provide a JSON schema and/or a natural-language prompt describing what to pull. Example: hyperbrowser_extract({ urls: ["https://example.com"], prompt: "Get the product name and price", schema: { type: "object", properties: { name…hyperbrowser_crawlCrawl a website starting from a URL, following links and scraping each page to markdown. Use maxPages to bound the crawl. Example: hyperbrowser_crawl({ url: "https://example.com", maxPages: 10, _apiKey: "your-key" })
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WebReaper
{
"mcpServers": {
"alex-on-ai-webreaper": {
"url": "https://api.openai.com/v1"
}
}
}
Hyperbrowser
{
"mcpServers": {
"hyperbrowser": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-hyperbrowser"
]
}
}
}
Frequently asked questions
WebReaper is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Hyperbrowser belongs to Search & Data Extraction and uses a local stdio subprocess. Pick WebReaper for search & data extraction work and Hyperbrowser for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
WebReaper is listed as free. Auth: api key required. Hyperbrowser has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add alex-on-ai-webreaper and hyperbrowser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WebReaper has a quality signal of 56/100 (Good) with 4 views, 0 installs and 152 GitHub stars. Hyperbrowser has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.