Web Search vs Nexus
A side-by-side look at the Web Search and Nexus MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Web Search for search & data extraction work over a hosted endpoint; choose Nexus 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 Web Search when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
GROUNDROUTE_API_KEY.
Choose Nexus 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:
OPENROUTER_API_KEY. - You want tools like
search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 36/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | GROUNDROUTE_API_KEY | OPENROUTER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 22 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Web Search | View Nexus |
Tools & capabilities
Web Search tools
No tool names declared yet. Check the project README from the listing page.
Nexus tools 1
searchThe main search tool that provides AI-powered search capabilities.
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.
Web Search
{
"mcpServers": {
"web-search": {
"url": "https://api.groundroute.ai/mcp"
}
}
}
Nexus
{
"mcpServers": {
"adawalli-nexus": {
"command": "bunx",
"args": [
"nexus-mcp"
],
"env": {
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Web Search is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Nexus belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Web Search for search & data extraction work and Nexus 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.
Web Search has no declared pricing — check the project's own site. Nexus is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 web-search and adawalli-nexus as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Web Search has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Nexus has 59/100 (Good) with 3 views, 0 installs and 22 GitHub stars.