Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG
Connect Wet to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. The wet mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
search — Web (SearXNG metasearch), news, images, academic research (Scholar / arXiv / PubMed / CrossRef / Semantic Scholar / BASE), library docs (HyDE +extract — URL -> smart chunks dict (clean_text + markdown + structured_data + code_blocks + metadata) via web-core 5-strategy chain. Batch processing (up to 50media — list (discover URLs from gallery pages), download (SSRF-safe). analyze was removed in v2.0.0 -- use imagine-mcp.understand insteadconfig — status, set, cache_clear, docs_reindex, warmup, setup_sync, setup_status, setup_skip, setup_reset, setup_completehelp — Per-tool documentation: search, extract, media, configconfig__open_relay — Re-trigger the zero-config relay setup flow (prints a fresh relay URL for the browser form). Registered via mcp-core's register_open_relay_tool so anConfiguration is passed through the environment: EMBEDDING_MODELS, RERANK_MODELS, LLM_MODELS, JINA_AI_API_KEY, GEMINI_API_KEY, PUBLIC_URL, GOOGLE_VERTEX_EXPRESS_API_KEY, OPENAI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wet's toolset — search, extract, media and 3 more — is a fair guide to whether it matches your workflow.
This entry was verified against Wet's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search | Web (SearXNG metasearch), news, images, academic research (Scholar / arXiv / PubMed / CrossRef / Semantic Scholar / BASE), library docs (HyDE + FTS5), find similar pages. Includes docs_resolve (library name -> ranked id) |
| extract | URL -> smart chunks dict (clean_text + markdown + structured_data + code_blocks + metadata) via web-core 5-strategy chain. Batch processing (up to 50 URLs), deep crawling, site mapping, local file conversion (PDF/DOCX/XL |
| media | list (discover URLs from gallery pages), download (SSRF-safe). analyze was removed in v2.0.0 -- use imagine-mcp.understand instead |
| config | status, set, cache_clear, docs_reindex, warmup, setup_sync, setup_status, setup_skip, setup_reset, setup_complete |
| help | Per-tool documentation: search, extract, media, config |
| config__open_relay | Re-trigger the zero-config relay setup flow (prints a fresh relay URL for the browser form). Registered via mcp-core's register_open_relay_tool so an LLM can restart setup without a manual restart. |
{
"mcpServers": {
"wet": {
"command": "uvx",
"args": ["wet-mcp"],
"env": {
"EMBEDDING_MODELS": "jina_ai/jina-embeddings-v5-text-small",
"RERANK_MODELS": "jina_ai/jina-reranker-v3",
"LLM_MODELS": "gemini/gemini-3-flash-preview",
"JINA_AI_API_KEY": "jina_xxx",
"GEMINI_API_KEY": "AIza_xxx"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| EMBEDDING_MODELS | Configuration value read at startup. | Optional |
| RERANK_MODELS | Configuration value read at startup. | Optional |
| LLM_MODELS | Configuration value read at startup. | Optional |
| JINA_AI_API_KEY | Credential the server authenticates with. | Yes |
| GEMINI_API_KEY | Credential the server authenticates with. | Yes |
| PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
| GOOGLE_VERTEX_EXPRESS_API_KEY | Credential the server authenticates with. | Yes |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.