Wet

WET - Web Extended Toolkit MCP Server

Distribution & CLI: the repo, CLI and Python module are wet. The PyPI distribution is `n24q02m-wet` (install pip install n24q02m-wet / uvx n24q02m-wet). wet is an HTTP-only MCP server: start it with wet server start and point clients at http://127.0.0.1:8000/mcp. There is no stdio mode; a bare wet prints the control-plane usage. The wet and wet-mcp aliases remain available.

mcp-name: io.github.n24q02m/wet

Open-source MCP server for AI agents: web search, content extraction, and library docs.

Current release: v3.x. media(action="analyze") was removed in the

v2.0.0 BREAKING release. Use

imagine-mcp's

understand action for vision/audio/video analysis. See

docs/migration.md for the upgrade recipe.

Sister projects from n24q02m (click to expand)

Table of contents

• Features
• Status
• Quick install
• Self-host usage
• Configuration
• Documentation
• Tools
• CLI
• Comparison
• Security
• Build from Source
• Trust Model
• License

Features

• Web Search -- Embedded SearXNG metasearch (Google, Bing, DuckDuckGo, Brave) with query expansion, TTL cache (1 h general / 5 min time-sensitive), standardized citation format, and 200-token snippet cap. Optional cloud search backends (Tavily, Brave, Exa, Kagi, OpenRouter, Firecrawl) as a fallback chain via SEARCH_BACKENDS
• Academic Research -- Search Google Scholar, Semantic Scholar, arXiv, PubMed, CrossRef, BASE
• Library Docs -- Auto-discover and index documentation with FTS5 hybrid search, HyDE-enhanced retrieval, and version-specific docs
• Content Extract -- 5-strategy escalation chain via n24q02m-web-core ScrapingAgent (basic_http -> tls_spoof -> render backends from BROWSER_BACKENDS (native / browserless / cf-browser-rendering) -> optional key-gated captcha), markitdown bridge for low-tier HTML/MD fallback, smart chunks structured output (clean text + markdown + JSON-LD + code blocks + metadata), batch processing (up to 50 URLs), deep crawling, site mapping
• Local File Conversion -- Convert PDF, DOCX, XLSX, CSV, HTML, EPUB, PPTX to Markdown
• Media -- List + download images / videos / audio files. analyze was removed in v2.0.0 -- use imagine-mcp.understand for vision/audio inference
• Anti-bot -- Stealth strategies bypass Cloudflare, Medium, LinkedIn, Twitter
• Zero Config -- Built-in local reference embedding + reranking through fastretrieval, no API keys needed. Optional cloud models configured per task via the [models.embed|rerank|chat|jev_score] cells in ~/.wet/config.toml (OpenRouter default; one OPENROUTER_API_KEY serves every cell)

Quick install

# Method 1 (default): plugin install via Claude Code

/plugin marketplace add n24q02m/claude-plugins /plugin install wet@n24q02m-plugins

Method 2 (CLI): start a local instance, then register its HTTP endpoint

uvx --python 3.13 --from n24q02m-wet wet server start claude mcp add --transport http wet http://127.0.0.1:8000/mcp

Method 3 (always-on): compose stack from a clone of this repo (token auth)

docker compose up --build -d

Method 4 (remote): point a client at an HTTP deployment

claude mcp add --transport http wet https:// /mcp

Every method needs a running instance: wet never runs as a client-spawned subprocess. Install matrix (all Streamable HTTP; see the Setup page for full steps):

Public OCI image publication is discontinued. Existing historical registry tags remain untouched; new container deployments build from source or use the Cloudflare-managed registry.

The HTTP endpoint speaks Streamable HTTP. With auth = "token" or "multi" the client sends Authorization: Bearer ; no-auth is loopback-only. Stand one up via Method 2 or 3.

Full setup matrices live at the canonical docs site mcp.n24q02m.com/servers/wet/setup/ and the paste-to-agent snippets at claude-plugins/plugins/wet/setup-with-agent.md (per Spec F single source of truth).

Self-host usage

Two supported ways to run the always-listening HTTP server. In both, the MCP endpoint is http://127.0.0.1:8000/mcp (Streamable HTTP) and the config root is ~/.wet/ (config.toml, docs.db, subs/). Never run the server as a spawned subprocess of a client — register the endpoint in your client instead.

Dev (uv, no-auth loopback)

git clone https://github.com/n24q02m/wet && cd wet

uv run wet config init # writes ~/.wet/config.toml (default: auth = "no-auth") uv run wet server start # serves http://127.0.0.1:8000/mcp (--foreground to stay attached)

no-auth refuses non-loopback binds — the server is localhost-only until you switch to token auth.

Always-on (docker)

# 1. Mint a token and its scrypt hash (hull-core canonical; the hash command

never echoes the token itself)

openssl rand -hex 32 # the token — give it to clients, keep it secret uv run wet token hash # paste the output as token_hash

2. Instance config from the example

cp docker-config/config.example.toml docker-config/config.toml

edit [server] token_hash and the [models.*] cells (see below)

3. Data continuity (optional): carry an existing instance over by copying

docs.db and subs/ into the wet-home named volume BEFORE first start:

docker volume create wet-wet-home && \ docker cp ~/.wet/docs.db wet-wet-home:/docs.db && \ docker cp ~/.wet/subs wet-wet-home:/subs # adjust: files land as root, chown 999:999

docker compose up -d --build

Compose publishes 127.0.0.1:${WET_PORT:-8000} → container 8000 (loopback only) and mounts docker-config/config.toml read-only at /home/appuser/.wet/config.toml. Persistent data (docs.db, subs/) lives in the wet-home named volume; the download/cache dir in wet-data. Editing the config takes effect on docker compose restart.

Consumers

# CLI (talks to the running server over HTTP; exits 2 with a hint when none runs):

uvx --python 3.13 --from n24q02m-wet wet search " "

MCP client (Claude Code):

claude mcp add --transport http wet http://127.0.0.1:8000/mcp \ --header "Authorization: Beare