A side-by-side look at the Crawdar MCP 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 Crawdar MCP 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.
research_businesses, search_businesses, sandbox_businesses.catalog_overview, discover_smart, inspect.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 59/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 9 | 4 |
| Full listing | View Crawdar MCP | View Looot |
research_businessesOne-call research from a natural-language brief.search_businessesStructured target and geography search.sandbox_businessesFictional integration test with no search-provider usage.start_lead_searchStart a private resumable job.get_lead_searchPoll status and page through compact or full results.refine_lead_searchCreate a revised job without changing the original.retry_lead_searchRecover from a stopped job.cancel_lead_searchCancel a queued or running job.explain_crawdarRead result semantics, limits, and safe-use guidance.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 `fallbackPaste 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.
{
"mcpServers": {
"eliottreich-crawdar-mcp": {
"command": "npx",
"args": [
"--yes",
"newman@6.2.1"
]
}
}
}
{
"mcpServers": {
"looot": {
"command": "npx",
"args": [
"-y",
"looot-mcp"
]
}
}
}