A side-by-side look at the Trieve and Google Web Search MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Trieve for search & data extraction work as a local process; choose Google Web Search for search & data extraction. You can also run both side by side in one mcpServers block.
OPENAI_API_KEY, LLM_API_KEY.Rows where the two servers differ are marked.
| Spec | G Google Web Search | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 47/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | OPENAI_API_KEYLLM_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,717 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Trieve | View Google Web Search |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"devflowinc-trieve": {
"command": "npx",
"args": [
"-y",
"mcp-eval"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"LLM_API_KEY": "YOUR_LLM_API_KEY_HERE"
}
}
}
}
No confirmed install command for Google Web Search yet — follow the setup steps linked from its listing page rather than a guessed package name.