A side-by-side look at the Sifter 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 Sifter 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 Sifter 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: SIFTER_API_KEY, SIFTER_DEFAULT_API_KEY.
No tool names declared yet. Check the project README from the listing page.
Fetch tools 9
create_entitiesCreate multiple new entities in the knowledge graph
create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voice
add_observationsAdd new observations to existing entities in the knowledge graph
delete_entitiesDelete multiple entities and their associated relations from the knowledge graph
delete_observationsDelete specific observations from entities in the knowledge graph
delete_relationsDelete multiple relations from the knowledge graph
read_graphRead the entire knowledge graph
search_nodesSearch for nodes in the knowledge graph based on a query
open_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.
Sifter 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 Sifter 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.
Sifter is listed as freemium — a free tier with paid plans. Auth: api key required. 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 sifter-ai-sifter and fetch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sifter has a quality signal of 55/100 (Good) with 1 views, 0 installs and 54 GitHub stars. Fetch has 90/100 (Excellent) with 4 views, 0 installs and 91,147 GitHub stars.