The web, wired
into your local agent.
wigolo is a local-first MCP server that hands any coding agent the whole web — search, fetch, crawl, extract, cache, and research. Built to stand with the best tools in the lane. No API keys. No cloud. No metered bill.
claude code · cursor · codex · gemini cli · vs code · windsurf · zed · antigravity
one command wires it into
Your agent is smart. Its web access isn't.
// every result explains itself { "excerpt": "Logical replication replicates data…", "score": 0.87, "breakdown": { "semantic": 0.91, "lexical": 0.74, "engine_consensus": "4/5 engines" }, "source_span": { "start": 1284, "end": 1571 }, "citation_id": "f38b44c100e4" }
Evidence, not blue links
See the receiptsOne MCP call fans a query array across many engines in parallel. Every result comes back with a transparent score breakdown, byte-offset source spans, and citation IDs — output your agent can quote.
↓ anti-bot challenge detected
↓ SPA shell · thin content
Routing on observable signals
How it worksThe fetch ladder escalates to a real browser on what it sees — SPA markers, challenge bodies, thin content — not domain guesses. It learns per-domain, and unlearns when a site stops needing it.
agent → cache "postgres logical replication" wigolo → 3 hits · hybrid keyword + semantic postgresql.org/docs/current/logical-replication postgresql.org/docs/current/warm-standby wiki.postgresql.org/wiki/Streaming_Replication latency → 3ms · $0 · nothing left your machine
Everything it sees, it keeps
Get startedEvery response lands in a local store under ~/.wigolo/ — full text, keyword index, and on-device vectors. Asking again is instant and costs nothing; find_similar and change detection build on it.
question → "how does postgres logical replication work?" decompose → 4 sub-queries · fanned out in parallel ▸ publication / subscription model ▸conflict handling & limitations ▸ vs. physical / streaming replication synthesize → cited brief · 7 sources · 12 citations gaps → surfaced, not hidden
Research that writes itself
All 10 toolsresearch decomposes a question, fans out sub-queries, fetches sources, and hands back a cited brief. agent runs an autonomous plan → search → fetch → extract → synthesize loop with a step log and time budget.
Free, and meant to
stay that way
wigolo is AGPL-3.0 — free to use, modify, and self-host, including inside a company. The license keeps it open: nobody can close it up and sell it back to you. Maintained, not paywalled.
“Verbatim quoted excerpts, pinned to byte-offset source spans with citation IDs.”
All four tools converged on the same core answer. wigolo · the only tool of four to return this
1 / 4Same fight.
Different physics.
The paid tools in this lane are genuinely good — that's what makes the parity interesting. What still separates wigolo isn't quality. It's where the work happens.
| wigolo | firecrawl | exa | tavily | |
|---|---|---|---|---|
| the fight — everyone shows up | ||||
| Multi-engine web search | ||||
| Fetch & structured extraction | ||||
| Whole-site crawl & map | — | |||
| the physics — where the work happens | ||||
| Verbatim excerpts pinned to byte-offset source spans | — | — | — | |
| Explainable per-result score decomposition | — | — | — | |
| Persistent local memory — instant, offline re-query | — | — | — | |
| Query data stays on your machine | — | — | — | |
| API key / account | none | required | required | required |
| Cost per query | $0 | metered | metered | metered |
Feature standing as of July 2026 — check each vendor's docs for current state. One cold query, four tools, judged on the evidence alone — watch the full run.
Give your agent the whole web.
One command installs the local engine and wires it into your agent — search, fetch, crawl, extract, cache, and research, with no API key.
Working in under two minutes.
Read the full CLI reference and docs on GitHubInstall & wire your agent
Any of these, comma-separated: claude-code · cursor · codex · gemini-cli · vscode · windsurf · zed · antigravity
That's the whole setup — search, fetch, crawl, extract & cache need no API key.
Check it's healthy
Verifies the local engine — search, browser, on-device models.
Node ≥ 20 · macOS / Linux / Windows · no account, no key.
Optional — answer synthesis
research, agent, and answer-format search use an LLM to write the final text. Any provider works — or stay fully local.
A free-tier key is plenty — or keyless with a local model server.
Found something?
Say it.
wigolo is in public beta — everything shipped works, and it's held to a 6,000-test suite, but beta means the polish is still being sanded. Every report is read, usually the same day.