What is the key difference between Wigolo and Lilbee?

Wigolo belongs to the Search & Data Extraction category with local stdio execution, while Lilbee belongs to the Search & Data Extraction category with local stdio execution.

How do I install Wigolo or Lilbee in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Wigolo and Lilbee free or paid?

Wigolo operates under a Freemium model (API Key required). Lilbee operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Wigolo lists 6 tools with 2 views and 5,212 GitHub stars. Lilbee lists 5 tools with 1 views and 53 GitHub stars.

Can I use both Wigolo and Lilbee together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Wigolo vs Lilbee

In-depth architectural comparison of the Wigolo and Lilbee MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Wigolo

Search & Data Extraction · Local stdio

Quality: 64/100 (Good) | Auth: API Key required

Lilbee

Search & Data Extraction · Local stdio

Quality: 60/100 (Good) | Auth: API Key required

Verdict Summary: Choose Wigolo if you need specialized Search & Data Extraction tools running via a local process. Choose Lilbee if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Wigolo when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: WIGOLO_LLM_PROVIDER, GEMINI_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, GROQ_API_KEY.
Primary tools included: Multi-engine web search with local ML reranking, JavaScript rendering for dynamic web pages, Persistent local SQLite cache for all data.

Explore Wigolo Details

Choose Lilbee when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: LILBEE_API_KEY, LILBEE_MODEL_PATH, LILBEE_GPU_DEVICES.

Feature & Specification Comparison

Specification	Wigolo KnockOutEZ Search & Data Extraction	Lilbee tobocop2 Search & Data Extraction
Summary	Local-first, keyless web intelligence in one server: search, fetch, crawl, extract, cache, find-similar, and research. Multi-engine search with local ML reranking and a persistent SQLite cache, renders JS-heavy pages, and keeps everything on your machine. Install via npx wigolo init --non-interactive --agents=.	Runs and manages its own local models, or uses your existing Ollama or LM Studio if you prefer. Indexes your files and code, crawls the websites you point it at, and answers with citations to the source.
Category & Scope

Tools & Capabilities Breakdown

Wigolo Tools (6)

Multi-engine web search with local ML reranking

JavaScript rendering for dynamic web pages

Persistent local SQLite cache for all data

Keyless operation for search, fetch, crawl, extract, cache, and find-similar

Optional LLM integration for research and synthesized answers

Supports integration with many MCP clients and agent frameworks

Lilbee Tools (5)

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Wigolo Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "knockoutez-wigolo": {
      "command": "npx",
      "args": [
        "-y",
        "wigolo"
      ],
      "env": {
        "WIGOLO_LLM_PROVIDER": "YOUR_WIGOLO_LLM_PROVIDER_HERE",
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
        "GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE"
      }
    }
  }
}

Lilbee Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tobocop2-lilbee": {
      "command": "npx",
      "args": [
        "-y",
        "lilbee"
      ],
      "env": {
        "LILBEE_API_KEY": "YOUR_LILBEE_API_KEY_HERE",
        "LILBEE_MODEL_PATH": "YOUR_LILBEE_MODEL_PATH_HERE",
        "LILBEE_GPU_DEVICES": "YOUR_LILBEE_GPU_DEVICES_HERE"
      }
    }
  }
}

Frequently Asked Questions

Wigolo is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Lilbee belongs to Search & Data Extraction using local stdio subprocess. Select Wigolo when you need capabilities focused on search & data extraction and Lilbee when you require tools for search & data extraction.

More alternatives to Wigolo More alternatives to Lilbee Search & Data Extraction category hub