Locus vs Apify MCP Server
A side-by-side look at the Locus and Apify MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Locus for search & data extraction work as a local process; choose Apify MCP Server 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 Locus when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Choose Apify 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: OAuth 2.0.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
title, readOnlyHint, true.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 45/100 · Fair | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | APIFY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 12,166 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 13 |
| Full listing | View Locus | View Apify MCP Server |
Tools & capabilities
Locus tools
No tool names declared yet. Check the project README from the listing page.
Apify MCP Server tools 13
titlereadOnlyHinttrueget-datasetfetch-actor-detailsapify--web-fetchapify--website-content-crawlerpageFunctioninitialCookiesopenWorldHintcall-actorsearch-actors- +1 more on 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.
Locus
{
"mcpServers": {
"locus-3": {
"command": "npx",
"args": [
"-y",
"plugins"
]
}
}
}
Apify MCP Server
{
"mcpServers": {
"apify-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Locus is categorized under Search & Data Extraction and uses a local stdio subprocess. Apify MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Locus for search & data extraction work and Apify MCP Server 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.
Locus has no declared pricing — check the project's own site. Apify MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 locus-3 and apify-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Locus has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Apify MCP Server has 68/100 (Great) with 5 views, 0 installs and 12,166 GitHub stars.