A side-by-side look at the Apify MCP Server 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 Apify MCP Server 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.
APIFY_TOKEN.title, readOnlyHint, true.catalog_overview, discover_smart, inspect.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 68/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12,166 | 3 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 13 | 4 |
| Full listing | View Apify MCP Server | View Looot |
titlereadOnlyHinttrueget-datasetfetch-actor-detailsapify--web-fetchapify--website-content-crawlerpageFunctioninitialCookiesopenWorldHintcall-actorsearch-actorscatalog_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": {
"apify-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"looot": {
"command": "npx",
"args": [
"-y",
"looot-mcp"
]
}
}
}