Wigolo

At a glance

Wigolo bundles the web jobs an agent keeps needing into one local server: search across many engines with its own reranking, page fetching that falls back to a headless browser when a site needs one, crawling, structured extraction, a searchable cache of everything it has read, and change tracking for pages you watch. Search, fetch, crawl and extract need no account or key.

The research and agent tools write a finished, cited answer only when you give them a model to use, such as a free Gemini key or a local Ollama model. Without one they hand the evidence back for your own assistant to write up. The first setup downloads a browser engine and small on-device models, about 1.5 GB in all.

Made by

KnockOutEZ (Towhid), open source with commercial licences available

Licence

AGPL-3.0-only

Latest version

0.3.1 (26 Oct 2026)

npm package

wigolo

GitHub stars

5.5K

Downloads

1.1K a week

Last commit

26 Oct 2026

Tools

10

Runs on

Your computer

Our check: We ran this exact config on 27 Oct 2026: it started and answered with 10 tools.

What's in the pod: its tools

We found 10 tools when we started it on 27 Oct 2026. 7 only read. The rest can change things, so keep your app's "ask before each tool call" setting on for them.

Grouped and described by us. The README on GitHub lists the inputs each tool takes.

Set it up

1. Run npx wigolo init once. It downloads the browser engine and models and checks each part. Add --agents=claude-code,cursor to write those clients' configs at the same time.
2. Add the config below to any other client.
3. Optional: set WIGOLO_LLM_PROVIDER and a matching key in env so the research and agent tools can write their own answers.

Pick your app for the exact snippet and where it goes.

{
  "mcpServers": {
    "wigolo": {
      "command": "npx",
      "args": [
        "-y",
        "wigolo"
      ]
    }
  }
}

claude mcp add-json wigolo '{"command":"npx","args":["-y","wigolo"]}'

{
  "mcpServers": {
    "wigolo": {
      "command": "npx",
      "args": [
        "-y",
        "wigolo"
      ]
    }
  }
}

{
  "servers": {
    "wigolo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "wigolo"
      ]
    }
  }
}

{
  "mcpServers": {
    "wigolo": {
      "command": "npx",
      "args": [
        "-y",
        "wigolo"
      ]
    }
  }
}

Run npx wigolo doctor if a tool reports a missing component. It names the part and the fix.

New to this? See the setup guides for Claude Code, Cursor, Claude Desktop and ChatGPT.

Settings

Names are exactly as the project spells them. Required ones are marked.

What it can touch

Safer setup: Nothing leaves your machine except the web requests themselves, unless you set an LLM provider, which then sees the gathered text. Use Ollama to keep that local too.

Before you start

• Node.js 22 or newer
• About 1.5 GB of free disk for the browser engine and models

If it does not work

A tool reports that a component is not ready

Run npx wigolo doctor. Setup never fails on a bad download; it reports what is missing and how to fix it.

research returns a brief instead of an answer

That is the keyless behaviour. Set WIGOLO_LLM_PROVIDER and a key, or let your own assistant write the answer from the brief.

Setup runs out of disk

It needs about 1.5 GB for the browser engine and models. Free some space, or run init with --no-warmup to delay the downloads.

You want to remove it

npx wigolo config --uninstall --yes removes everything it installed.

Peas in a pod: similar servers

How Wigolo lines up against other browser and web data servers on the shelf.

Questions

Something wrong on this page? Tell us.