What does the wigolo mcp server do?

It connects Wigolo to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Wigolo directly.

How do I install the wigolo mcp server?

Run it through your MCP client's configuration using `npx -y wigolo`. Add the server block to Claude Desktop's config file (or use `claude mcp add` for Claude Code), restart the client, and the tools appear automatically. Full snippets are on this page.

What credentials does it need?

It reads `WIGOLO_LLM_PROVIDER`, `GEMINI_API_KEY`, `WIGOLO_SEARCH`, `WIGOLO_GITHUB_TOKEN`, `WIGOLO_TLS_TIER`, `WIGOLO_EAGER_WARMUP`, `WIGOLO_API_TOKEN`, `PROXY_URL` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

Wigolo MCP Server — Install Guide & Tools

Name: Wigolo MCP Server
Author: KnockOutEZ

What is the Wigolo MCP server?

Local-first web intelligence MCP server for AI coding agents. Exposed over MCP by the wigolo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Local-first web intelligence for AI agents — no keys, no cloud, no metered bill.

Built for agents. — One MCP call fans out many queries across many engines in parallel, which a serial host tool-loop can't replicate. Every result carries transparent per-result scoring, and output is budget-aware
Honest output. — Stale cache, failed fetches, degraded backends, and truncation are surfaced in the result. When a bot-protected page can't be read, you get a labeled blocked_by_challenge failure, not a challenge shell returned as content
$0 per query, free to re-query. — Default search talks to public engines through direct adapters; the reranker and embeddings run on-device. Every response is cached, so asking again is instant and costs nothing
Private by default. — Cache, embeddings, models, and config live under ~/.wigolo/. Nothing reaches a third party unless you explicitly opt into an LLM for synthesis

Configuration

You will need 8 environment variables: WIGOLO_LLM_PROVIDER, GEMINI_API_KEY, WIGOLO_SEARCH, WIGOLO_GITHUB_TOKEN, WIGOLO_TLS_TIER, WIGOLO_EAGER_WARMUP, WIGOLO_API_TOKEN, PROXY_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by KnockOutEZ; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Wigolo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
MCP clients confirm each tool call by default. Leave that on until you have watched what the wigolo mcp server does with a few real requests.

How to install the Wigolo MCP server

{
  "mcpServers": {
    "wigolo": {
      "command": "npx",
      "args": ["-y", "wigolo"],
      "env": {
        "WIGOLO_LLM_PROVIDER": "your-value",
        "GEMINI_API_KEY": "your-value",
        "WIGOLO_SEARCH": "your-value",
        "WIGOLO_GITHUB_TOKEN": "your-value",
        "WIGOLO_TLS_TIER": "your-value",
        "WIGOLO_EAGER_WARMUP": "your-value",
        "WIGOLO_API_TOKEN": "your-value",
        "PROXY_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

Variable	Description	Required
WIGOLO_LLM_PROVIDER	Configuration value read at startup.	Optional
GEMINI_API_KEY	Credential the server authenticates with.	Yes
WIGOLO_SEARCH	Configuration value read at startup.	Optional
WIGOLO_GITHUB_TOKEN	Credential the server authenticates with.	Yes
WIGOLO_TLS_TIER	Configuration value read at startup.	Optional
WIGOLO_EAGER_WARMUP	Configuration value read at startup.	Optional
WIGOLO_API_TOKEN	Credential the server authenticates with.	Yes
PROXY_URL	Endpoint or connection string the server talks to.	Yes

Wigolo MCP Server

What is the Wigolo MCP server?

What it actually does

Configuration

Adding it to your client

When to reach for it

Caveats

How to install the Wigolo MCP server

Configuration

Frequently asked questions

Alternatives to the Wigolo MCP server

Fonoster

Exa

Perplexity

ElevenLabs

E2B

Hugging Face