Scrapeless MCP Server vs Spider Cloud
A side-by-side look at the Scrapeless MCP Server and Spider Cloud MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Scrapeless MCP Server for search & data extraction work as a local process; choose Spider Cloud 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 Scrapeless MCP Server 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:
SCRAPELESS_API_KEY, BROWSER_PROFILE_ID, BROWSER_PROFILE_PERSIST, BROWSER_SESSION_TTL.
SChoose Spider Cloud when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Spider Cloud | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 59/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | OAuth 2.0 |
| Pricing | Freemium | Not declared |
| Required env vars | SCRAPELESS_API_KEYBROWSER_PROFILE_IDBROWSER_PROFILE_PERSISTBROWSER_SESSION_TTL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 169 | — |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Scrapeless MCP Server | View Spider Cloud |
Tools & capabilities
Scrapeless MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Spider Cloud 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.
Scrapeless MCP Server
{
"mcpServers": {
"scrapeless-ai-scrapeless-mcp-server": {
"command": "npx",
"args": [
"-y",
"scrapeless-mcp-server"
],
"env": {
"SCRAPELESS_API_KEY": "YOUR_SCRAPELESS_API_KEY_HERE",
"BROWSER_PROFILE_ID": "YOUR_BROWSER_PROFILE_ID_HERE",
"BROWSER_PROFILE_PERSIST": "YOUR_BROWSER_PROFILE_PERSIST_HERE",
"BROWSER_SESSION_TTL": "YOUR_BROWSER_SESSION_TTL_HERE"
}
}
}
}
Spider Cloud
{
"mcpServers": {
"spider-cloud": {
"url": "https://spider.cloud/mcp"
}
}
}