wigolo is in public beta — everything works, and it's improving fast. Hit a rough edge? Tell us

public beta · free · open source

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

Get started
your agent — wigolo mcp · no API keys
$0
per query, forever
0
API keys to get started
10
web tools over one MCP

one command wires it into

The tools

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 receipts

One 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.

1
Plain HTTPfast path — most pages end here

↓ anti-bot challenge detected

2
TLS-impersonationlearned fingerprints past bot walls

↓ SPA shell · thin content

3
Headless browserfull render from a warm in-process pool

Routing on observable signals

How it works

The 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 started

Every 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 tools

research 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.

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 / 4
Parity

Same 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.

wigolofirecrawlexatavily
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 / accountnonerequiredrequiredrequired
Cost per query$0meteredmeteredmetered

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.

The meter: a metered cloud API's cost climbs with every query while wigolo stays flat at zero dollars — illustrative pricing
Ask twice, pay never: first query hits the live web in 3.6 seconds, the second answers from local cache in milliseconds, the third still answers offline

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.

1

Install & 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.

2

Check it's healthy

Verifies the local engine — search, browser, on-device models.

Node ≥ 20 · macOS / Linux / Windows · no account, no key.

3

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.