One Search MCP vs Web Search Plus MCP
A side-by-side look at the One Search MCP and Web Search Plus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose One Search MCP for search & data extraction work as a local process; choose Web Search Plus MCP 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 One Search MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
Choose Web Search Plus MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YOU_API_KEY, SERPER_API_KEY, LINKUP_API_KEY. - You want tools like
web_search, web_extract.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 48/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | YOU_API_KEYSERPER_API_KEYLINKUP_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 146 | 5 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View One Search MCP | View Web Search Plus MCP |
Tools & capabilities
One Search MCP tools
No tool names declared yet. Check the project README from the listing page.
Web Search Plus MCP tools 2
web_searchSource-only web search through the Web Search Plus v3 runtime. Routes across configured source-result providers and returns additive v3 evidence, routing receipts, provider attempts, cache provenance, and typed errors.web_extractSource-only URL extraction through 9 Web Search Plus v3 providers. Responses preserve bounded-context limits, truncation warnings, evidence, and page-on-demand stored-content references.
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.
One Search MCP
{
"mcpServers": {
"one-search-mcp": {
"command": "npx",
"args": [
"-y",
"agent-browser"
]
}
}
}
Web Search Plus MCP
{
"mcpServers": {
"robbyczgw-cla-web-search-plus-mcp": {
"command": "uvx",
"args": [
"web-search-plus-mcp"
],
"env": {
"YOU_API_KEY": "YOUR_YOU_API_KEY_HERE",
"SERPER_API_KEY": "YOUR_SERPER_API_KEY_HERE",
"LINKUP_API_KEY": "YOUR_LINKUP_API_KEY_HERE"
}
}
}
}
Frequently asked questions
One Search MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Web Search Plus MCP belongs to Search & Data Extraction and uses a local stdio subprocess. Pick One Search MCP for search & data extraction work and Web Search Plus MCP 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.
One Search MCP has no declared pricing — check the project's own site. Web Search Plus MCP has no declared pricing — check the project's own site. 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 one-search-mcp and robbyczgw-cla-web-search-plus-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, One Search MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 146 GitHub stars. Web Search Plus MCP has 57/100 (Good) with 2 views, 0 installs and 5 GitHub stars.