SmartFetch vs WebReaper
A side-by-side look at the SmartFetch and WebReaper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SmartFetch for search & data extraction work as a local process; choose WebReaper for search & data extraction over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SmartFetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 40/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed |
Tools & capabilities
SmartFetch tools
No tool names declared yet. Check the project README from the listing page.
WebReaper 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.
SmartFetch
{
"mcpServers": {
"smartfetch": {
"command": "npx",
"args": [
"-y",
"agentcash@latest"
]
}
}
}
WebReaper
{
"mcpServers": {
"alex-on-ai-webreaper": {
"url": "https://api.openai.com/v1"
}
}
}
Frequently asked questions
SmartFetch is categorized under Search & Data Extraction and uses a local stdio subprocess. WebReaper belongs to Search & Data Extraction and uses a remote HTTP/SSE transport. Pick SmartFetch for search & data extraction work and WebReaper 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.
SmartFetch has no declared pricing — check the project's own site. WebReaper is listed as free. 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 smartfetch and alex-on-ai-webreaper as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SmartFetch has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. WebReaper has 56/100 (Good) with 4 views, 0 installs and 150 GitHub stars.