Locus vs Fetch
A side-by-side look at the Locus and Fetch 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 Fetch 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 Fetch 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.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 45/100 · Fair | 90/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,405 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Locus | View Fetch |
Tools & capabilities
Locus tools
No tool names declared yet. Check the project README from the listing page.
Fetch tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
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"
]
}
}
}
Fetch
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Locus is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Locus for search & data extraction work and Fetch 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. Fetch 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 locus-3 and fetch 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. Fetch has 90/100 (Excellent) with 5 views, 0 installs and 91,405 GitHub stars.