wigolo
A local web engine for the agent over MCP: search, fetch, crawl, extract and research with no keys and no cloud
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Goes to the network, fetches and crawls pages
- Downloads a browser engine and models to the machine
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/wigoloDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport stdio wigolo -- npx -y wigoloOr add to the file .mcp.json, in the project
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"wigolo","type":"stdio","command":"npx","args":["-y","wigolo"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"wigolo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add wigolo -- npx -y wigoloOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.wigolo]
command = "npx"
args = ["-y", "wigolo"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"wigolo": {
"type": "local",
"command": [
"npx",
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"wigolo": {
"command": "npx",
"args": [
"-y",
"wigolo"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Set up the engine and wire agents in one command: npx wigolo init --agents=claude-code,cursor. Any other MCP client registers npx -y wigolo in its config. Check health with npx wigolo doctor.
Other ways from the author
npx wigolo init --agents=claude-code,cursorSets up the local engine and writes the MCP config for the chosen agents.
This is third-party code. Review the repository files before installing.
What it does
wigolo gives the agent one surface for everything web: search, fetch, crawl, extract, cache, find-similar, research and autonomous gather loops. It runs where the agent runs: as an MCP server next to a coding agent, as a REST or MCP endpoint for self-hosted agents or embedded through an SDK. The core tools need no keys, nothing it touches leaves the ~/.wigolo directory, and the bill does not grow with the number of queries. The init command sets up the local engine, downloads a browser engine and models and can write the MCP config for the agents you name. For synthesized answers in research and agent you can add a free model key; without it you get raw material back.
Who it is for. For developers and agent owners who want private web access without paid search APIs or the cloud.
Good fit when
- You want the agent to search and read the web without keys or per-query billing
- You need local crawling and data extraction from pages
- You want topic research with a cache and no data leaving for the cloud
Not a fit when
- You lack about 1.5 GB of space and Node 20 or newer
- You need synthesized answers without your own model key: you will get only raw material
Example request
Search the web for recent material on the topic, synthesize it and cite the sourcesLimitations
The project is in public beta. It needs Node 20 or newer and about 1.5 GB of disk for the browser engine and models. Search, fetch, crawl, extract, cache and find-similar are keyless, while research, agent and the answer mode use a model and need a free key, otherwise they return a raw brief. Data stays in the ~/.wigolo directory.
How to disable. Run npx wigolo config --uninstall --yes and remove the wigolo entry from the MCP client config.
MCP
- Transport
- stdio, http
- Authentication
- not required
| Environment variables | |
|---|---|
| GEMINI_API_KEY secret | A free model key for synthesized answers in research and agent |
Security check
- Goes to the network, fetches and crawls pages
- Downloads a browser engine and models to the machine
README in short
The README describes wigolo as a local web engine for agents: search, fetch, crawl, extract, cache, find-similar, research and gather loops through one interface. It runs as an MCP server next to the agent, as a REST or MCP endpoint and through SDKs for Python, TypeScript, LangChain, CrewAI, LlamaIndex, the Vercel AI SDK and n8n. The init command sets up the engine and writes config for the chosen agents, and doctor checks health. Core tools are keyless; synthesized answers need a model key. The package is on npm, AGPL-3.0 licensed.
FAQ
Do I need keys or billing?
The core tools work with no keys and no per-query billing. A model key is only needed for synthesized answers in research and agent.
Where does data go?
Nothing leaves the local ~/.wigolo directory; the engine runs on your machine.
Related
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills