A side-by-side look at the Data Gleaner and Scrapercity Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Data Gleaner for search & data extraction work; choose Scrapercity Cli for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
SCRAPERCITY_API_KEY.Apollo, BuiltWith.Rows where the two servers differ are marked.
| Spec | D Data Gleaner | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 36/100 · Fair | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | SCRAPERCITY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Data Gleaner | View Scrapercity Cli |
No tool names declared yet. Check the project README from the listing page.
ApolloB2B contacts by job title, industry, locationBuiltWithAll sites using a technologyPaste 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.
No confirmed install command for Data Gleaner yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"scrapercity-scrapercity-cli": {
"command": "npx",
"args": [
"-y",
"scrapercity"
],
"env": {
"SCRAPERCITY_API_KEY": "YOUR_SCRAPERCITY_API_KEY_HERE"
}
}
}
}