← Back to directory

wigolo

Community

Local-first web intelligence for AI coding agents.

GitHub source repository ↗

★ 3.5k Stars Category · Dev Tools Very popular

57FMRS · C

Reliability

8/20

Security and permissions

11/20

Maintenance

10/20

Documentation

15/20

Setup experience

13/20

The supplied material describes wigolo as a KnockOutEZ-maintained public-beta, local-first web-intelligence MCP server. It supports stdio MCP and exposes SSE for remote MCP clients through its server mode; core search, fetch, crawl, extract, cache, and similarity features require no API key. Research and autonomous-agent synthesis can optionally use an LLM provider.

Read the FMRS scoring method →

wigolo is a local MCP and REST web-intelligence server for AI agents. It provides search, fetching, crawling, structured extraction, caching, similarity search, research, autonomous gathering, and page change monitoring. Core tools work without API keys, while cache, embeddings, models, and configuration are stored by default under ~/.wigolo/. The project is in public beta, requires Node.js 20 or newer, and needs about 1.5 GB of free disk space.

Tools

Runs parallel multi-engine search with rank fusion, reranking, and explainable result scores.

fetch

Loads a URL through a tiered HTTP and headless-browser router and returns cleaned Markdown, metadata, and links.

crawl

Crawls multiple pages using BFS, DFS, sitemap, or map-only modes while respecting robots.txt and per-domain rate limits.

extract

Extracts tables, metadata, JSON-LD, brand identity, named schemas, or custom JSON Schema data from a page.

cache

Searches previously seen content using keyword or hybrid semantic retrieval and supports statistics, clearing, and change detection.

find_similar

Finds pages similar to a URL or concept using keyword, semantic, and live-web fusion.

research

Decomposes a question, expands subqueries, fetches sources, and produces a cited report or structured brief.

agent

Runs an autonomous gather loop covering planning, search, fetching, extraction, and synthesis with a step log and time budget.

diff

Shows what changed on a page since the previous visit.

watch

Rechecks pages on demand and can deliver changes to a webhook.

Setup

Install Node.js 20 or newer, then run npx wigolo init. The command sets up the local engine, downloads the browser engine and on-device models, and performs a health check. Use --agents=claude-code,cursor or another supported comma-separated list to wire agent configurations during setup. Other MCP clients can register npx -y wigolo in their own MCP configuration. Run npx wigolo doctor to check health.

Fit and risk

Best for

Developers who prioritize local processing and privacy
Agents that need web tooling without per-query charges
Teams needing search, crawling, caching, and research in one surface
macOS, Linux, or Windows users with about 1.5 GB of available disk space

Not for

Users seeking a fully hosted service without local browser or model downloads
Workflows that require guaranteed access to every anti-bot or challenge-protected site
Environments that prohibit public-web crawling or optional third-party LLM synthesis
Users who need to keep a modified network-service version closed source

Required permissions

Local filesystem access is needed for cache, configuration, embeddings, and models under ~/.wigolo/.
Network access is needed to search and retrieve the public web.
Browser mode may start a local browser engine; Linux may require additional operating-system libraries.
Research, agent, and answer-format search can optionally call Gemini, Anthropic, OpenAI, Groq, Ollama, or another compatible provider.
Authenticated pages and page actions may require session information.

Risks and side effects

Public search engines and target sites may fail, become stale, rate-limit requests, or block access; wigolo reports degradation and challenge failures in its output.
Datacenter IP reputation can reduce access to challenge-protected sites.
Optional LLM synthesis sends relevant requests to the selected provider; Ollama or another compatible local endpoint can keep synthesis local.
Browser and model downloads require about 1.5 GB of disk space.
The project uses AGPL-3.0-only; modified versions run as network services must publish their modifications.

Troubleshooting

Run npx wigolo doctor to inspect component health.
Retry failed downloads with wigolo warmup --all, or with --browser, --embeddings, or --reranker.
If the browser will not launch on Linux, run wigolo warmup --browser and install the reported system libraries.
For native build errors or unusual Node versions, use Node 20, 22, or 24 LTS.
Behind a proxy, set USE_PROXY=true and PROXY_URL; TLS-inspecting proxies may also require NODE_EXTRA_CA_CERTS.
Use --no-warmup to defer downloads until first use.

Use cases

Providing AI coding agents with local web search and fetching

Crawling websites and extracting structured data

Building local RAG, research, or autonomous information-gathering workflows

Integrating self-hosted agents through MCP, REST, or SDKs

Supported clients

Claude CodeFull support

CursorFull support

CodexFull support

Gemini CLIFull support

VS CodeFull support

WindsurfFull support

ZedFull support

AntigravityFull support

Any MCP clientFull support

Related MCP servers

Compare with other MCP servers