WET - Web Extended Toolkit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEYS | No | LLM API keys for SDK mode (format: ENV_VAR:key,...) | |
| CACHE_DIR | No | Data directory for cache DB, docs DB, downloads (optional) | ~/.wet-mcp |
| LOG_LEVEL | No | Logging level | INFO |
| WET_CACHE | No | Enable/disable web cache (optional) | true |
| LLM_MODELS | No | LiteLLM model for media analysis (optional) | gemini/gemini-3-flash-preview |
| LLM_API_KEY | No | Custom LLM endpoint key (optional) | |
| SEARXNG_URL | No | External SearXNG URL (optional, when auto disabled) | http://localhost:41592 |
| SYNC_FOLDER | No | Remote folder name | wet-mcp |
| SYNC_REMOTE | No | rclone remote name | gdrive |
| DOCS_DB_PATH | No | Docs database location (optional) | ~/.wet-mcp/docs.db |
| DOWNLOAD_DIR | No | Media download directory (optional) | ~/.wet-mcp/downloads |
| GITHUB_TOKEN | No | GitHub personal access token for library discovery (optional, increases rate limit from 60 to 5000 req/hr). Auto-detected from `gh auth token` if GitHub CLI is installed. | |
| LLM_API_BASE | No | Custom LLM endpoint URL (optional, for SDK mode) | |
| RERANK_MODEL | No | LiteLLM rerank model (auto: cohere/rerank-multilingual-v3.0 if Cohere key in API_KEYS) | |
| RERANK_TOP_N | No | Return top N results after reranking | 10 |
| SYNC_ENABLED | No | Enable rclone sync | false |
| TOOL_TIMEOUT | No | Tool execution timeout in seconds, 0=no timeout (optional) | 120 |
| SYNC_INTERVAL | No | Auto-sync interval in seconds (0=manual) | 300 |
| SYNC_PROVIDER | No | rclone provider type (drive, dropbox, s3, etc.) | drive |
| EMBEDDING_DIMS | No | Embedding dimensions (optional, default auto=768) | 0 |
| RERANK_API_KEY | No | Custom rerank endpoint key (optional) | |
| RERANK_BACKEND | No | litellm or local. Auto: Cohere key in API_KEYS -> litellm, else local | |
| RERANK_ENABLED | No | Enable reranking after search | true |
| EMBEDDING_MODEL | No | LiteLLM embedding model (optional) | |
| RERANK_API_BASE | No | Custom rerank endpoint URL (optional, for SDK mode) | |
| SEARXNG_TIMEOUT | No | SearXNG request timeout in seconds (optional) | 30 |
| WET_AUTO_SEARXNG | No | Auto-start embedded SearXNG subprocess | true |
| WET_SEARXNG_PORT | No | SearXNG port (optional) | 41592 |
| EMBEDDING_API_KEY | No | Custom embedding endpoint key (optional) | |
| EMBEDDING_BACKEND | No | litellm (cloud API) or local (Qwen3). Auto: API_KEYS -> litellm, else local | |
| LITELLM_PROXY_KEY | No | LiteLLM Proxy virtual key (e.g. sk-...) | |
| LITELLM_PROXY_URL | No | LiteLLM Proxy URL (e.g. http://10.0.0.20:4000). Enables proxy mode | |
| EMBEDDING_API_BASE | No | Custom embedding endpoint URL (optional, for SDK mode) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| config__open_relayA | Get the relay configuration URL for wet-mcp, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status. |
| searchA | Find information across web, academic sources, or library docs. Returns search result listings (titles, URLs, snippets) -- NOT full page content. To read full content from a URL, use the Actions:
Key parameters:
Use |
| extractA | Read and return full page content from URLs or local files. Use this when you have a specific URL and need its content. For finding URLs first, use the Actions:
Key parameters:
Use |
| mediaA | Discover and download media files (images, videos, audio) from web pages. Actions:
Key parameters:
Typical workflow: list (discover) -> download (save locally). For LLM analysis (vision/audio/video), hand the downloaded path to imagine-mcp's understand action. The legacy media(action="analyze") was REMOVED in wet v2.0.0 (deprecated since v1.x.y); calling it now returns the standard unknown-action error. Use |
| helpA | Get detailed documentation for any tool. Call this when you need full parameter reference or usage examples. Valid tool_name values: search, extract, media, config. Quick guide -- which tool to use:
|
| configC | Server config and management. Actions: status|set|cache_clear|docs_reindex|warmup|setup_sync|setup_status|setup_start|setup_skip|setup_reset|setup_complete. Use help tool with tool_name='config' for full docs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Top-level tools are cleanly separated by intent (search finds URLs, extract reads content, media handles files, config manages the server, help documents everything), and descriptions explicitly cross-reference each other. Minor overlap remains: extract's `agent` action bundles search+extract, and config__open_relay overlaps the config tool's setup domain.
Names and all internal actions are consistently lowercase snake_case (docs_query, cache_clear, extract_structured, setup_sync). The one deviation is `config__open_relay`, whose double-underscore namespace prefix breaks the single-word pattern of every other top-level tool.
Six top-level tools sit squarely in the ideal 3-15 range and are well-scoped via an action-based dispatch pattern. However this count is somewhat deceptive, since extract (9 actions), search (7), and config (11) each pack a large hidden surface, making the set heavier than six names suggest.
The surface covers the full web-toolkit lifecycle: discovery (search/research/docs/similar), retrieval and parsing (extract/crawl/map/convert/structured), interaction (interact), change tracking (diff), media (list/download), and server management (config/help). Gaps are minor, e.g. no dedicated result-history or cache-inspection tool beyond config's status.