TinySearch vs Nexus
A side-by-side look at the TinySearch 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 TinySearch for search & data extraction work as a local process; 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 TinySearch 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.
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 | 56/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed |
Tools & capabilities
TinySearch 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.
TinySearch
{
"mcpServers": {
"marcellm01-tinysearch": {
"command": "uvx",
"args": [
"--from",
"tinysuite-search[server]",
"tinysearch"
]
}
}
}
Nexus
{
"mcpServers": {
"adawalli-nexus": {
"command": "bunx",
"args": [
"nexus-mcp"
],
"env": {
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
TinySearch is categorized under Search & Data Extraction and uses a local stdio subprocess. Nexus belongs to Search & Data Extraction and uses a local stdio subprocess. Pick TinySearch 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.
TinySearch is listed as free. Auth: no auth required. 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 marcellm01-tinysearch and adawalli-nexus as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TinySearch has a quality signal of 56/100 (Good) with 2 views, 0 installs and 230 GitHub stars. Nexus has 59/100 (Good) with 3 views, 0 installs and 23 GitHub stars.