Rag vs Wigolo
A side-by-side look at the Rag 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 Rag for search & data extraction work; 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 Rag when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You want tools like
list_knowledge_bases, search_documents, get_document_chunk.
Choose Wigolo 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 41/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,502 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Rag | View Wigolo |
Tools & capabilities
Rag tools 7
list_knowledge_basesList all available KBs with status (file/chunk counts, indexing status)search_documentsHybrid BM25 + vector search with RRF. Supports `search_mode`: `auto`, `bm25`, `vectorget_document_chunkRetrieve full content of a specific chunk by IDstart_reindexQueue an indexing request. Scope merge, force/deferred flags, orchestrator auto-spawncancel_reindexRemove a pending (not-yet-started) queue entryget_index_infoIndex metadata, queue state (status/position/deferred/last_error), contextualization healthcheck_changesDry-run filesystem scan. Lightweight, no API calls
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.
Rag
No confirmed install command for Rag yet — follow the setup steps linked from its listing page rather than a guessed package name.
Wigolo
{
"mcpServers": {
"knockoutez-wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}
Frequently asked questions
Rag is categorized under Search & Data Extraction and uses an install path we have not confirmed yet. Wigolo belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Rag 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. Rag has no confirmed install command yet — follow its own setup instructions.
Rag has no declared pricing — check the project's own site. 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 rag and knockoutez-wigolo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rag has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Wigolo has 64/100 (Good) with 3 views, 0 installs and 5,502 GitHub stars.