CRW Web Scraper vs Looot
A side-by-side look at the CRW Web Scraper and Looot MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CRW Web Scraper for search & data extraction work as a local process; choose Looot 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 CRW Web Scraper when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Choose Looot when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
catalog_overview, discover_smart, inspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 51/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,161 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View CRW Web Scraper | View Looot |
Tools & capabilities
CRW Web Scraper tools
No tool names declared yet. Check the project README from the listing page.
Looot tools 4
catalog_overviewcategories, platforms and jobs with counts and cheapest pricesdiscover_smartranks a shortlist against a plain-English use caseinspectinput and output schema, price formula, estimated max costrunholds the estimated cost, runs, settles; accepts `job:<id>` and `fallback
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.
CRW Web Scraper
{
"mcpServers": {
"crw-web-scraper": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
]
}
}
}
Looot
{
"mcpServers": {
"looot": {
"command": "npx",
"args": [
"-y",
"looot-mcp"
]
}
}
}
Frequently asked questions
CRW Web Scraper is categorized under Search & Data Extraction and uses a local stdio subprocess. Looot belongs to Search & Data Extraction and uses a local stdio subprocess. Pick CRW Web Scraper for search & data extraction work and Looot 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.
CRW Web Scraper has no declared pricing — check the project's own site. Looot is listed as a paid service. Auth: oauth 2.0. 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 crw-web-scraper and looot as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CRW Web Scraper has a quality signal of 51/100 (Good) with 1 views, 0 installs and 1,161 GitHub stars. Looot has 61/100 (Good) with 3 views, 0 installs and 3 GitHub stars.