CRW Web Scraper vs Lilbee
A side-by-side look at the CRW Web Scraper and Lilbee 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 Lilbee 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.
- Its auth model fits you: API key required.
- You have the keys it needs:
CRW_API_KEY, CRW_NO_AGENTS.
Choose Lilbee when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CRW_API_KEYCRW_NO_AGENTS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,172 | 65 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CRW Web Scraper | View Lilbee |
Tools & capabilities
CRW Web Scraper tools
No tool names declared yet. Check the project README from the listing page.
Lilbee 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.
CRW Web Scraper
{
"mcpServers": {
"crw-web-scraper": {
"command": "npx",
"args": [
"-y",
"crw-mcp@latest"
],
"env": {
"CRW_API_KEY": "YOUR_CRW_API_KEY_HERE",
"CRW_NO_AGENTS": "YOUR_CRW_NO_AGENTS_HERE"
}
}
}
}
Lilbee
{
"mcpServers": {
"tobocop2-lilbee": {
"command": "npx",
"args": [
"-y",
"lilbee"
]
}
}
}
Frequently asked questions
CRW Web Scraper is categorized under Search & Data Extraction and uses a local stdio subprocess. Lilbee belongs to Search & Data Extraction and uses a local stdio subprocess. Pick CRW Web Scraper for search & data extraction work and Lilbee 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. Auth: api key required. Lilbee is listed as free. Auth: no auth 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 crw-web-scraper and tobocop2-lilbee 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 53/100 (Good) with 1 views, 0 installs and 1,172 GitHub stars. Lilbee has 59/100 (Good) with 2 views, 0 installs and 65 GitHub stars.