WebReaper vs Spicrawl
A side-by-side look at the WebReaper and Spicrawl 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 Spicrawl 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 Spicrawl when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SPICRAWL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 56/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | Freemium |
| Required env vars | WEBREAPER_MCP_TOKEN | SPICRAWL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 150 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View WebReaper | View Spicrawl |
Tools & capabilities
WebReaper tools
No tool names declared yet. Check the project README from the listing page.
Spicrawl tools
No tool names declared yet. Check the project README from the listing page.
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"
}
}
}
Spicrawl
{
"mcpServers": {
"spicrawl": {
"command": "npx",
"args": [
"-y",
"@spicrawl/mcp"
],
"env": {
"SPICRAWL_API_KEY": "YOUR_SPICRAWL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
WebReaper is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Spicrawl belongs to Search & Data Extraction and uses a local stdio subprocess. Pick WebReaper for search & data extraction work and Spicrawl 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. Spicrawl is listed as freemium — a free tier with paid plans. Auth: api key required. 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 spicrawl 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 150 GitHub stars. Spicrawl has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.