TinySearch vs Wigolo — MCP Server Comparison | AllMCPs
TinySearch vs Wigolo
A side-by-side look at the TinySearch and Wigolo 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 Wigolo 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.
No tool names declared yet. Check the project README from the listing page.
Wigolo tools
No tool names declared yet. Check the project README from the listing page.
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 is categorized under Search & Data Extraction and uses a local stdio subprocess. Wigolo belongs to Search & Data Extraction and uses a local stdio subprocess. Pick TinySearch for search & data extraction work and Wigolo 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. Wigolo 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 marcellm01-tinysearch and knockoutez-wigolo 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. Wigolo has 64/100 (Good) with 3 views, 0 installs and 5,467 GitHub stars.