mcp-webgate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBGATE_DEBUG | No | Enable structured debug logging (default: false) | |
| WEBGATE_TRACE | No | Include content in summarized citations; also activates debug logging (default: false) | |
| WEBGATE_LOG_FILE | No | Log file path (empty = stderr) | |
| WEBGATE_LLM_MODEL | No | Model name (default: llama3.2) | |
| WEBGATE_SERPAPI_GL | No | SerpAPI country code (default: us) | |
| WEBGATE_SERPAPI_HL | No | SerpAPI language (default: en) | |
| WEBGATE_EXA_API_KEY | No | Exa API key | |
| WEBGATE_LLM_API_KEY | No | API key (empty for local models) | |
| WEBGATE_LLM_ENABLED | No | Enable LLM features (default: false) | |
| WEBGATE_LLM_TIMEOUT | No | LLM request timeout in seconds (default: 30) | |
| WEBGATE_SEARXNG_URL | No | SearXNG instance URL (default: http://localhost:8080) | |
| WEBGATE_LLM_BASE_URL | No | OpenAI-compatible endpoint (default: http://localhost:11434/v1) | |
| WEBGATE_BRAVE_API_KEY | No | Brave Search API key | |
| WEBGATE_SEARCH_TIMEOUT | No | HTTP request timeout in seconds (default: 8) | |
| WEBGATE_SERPAPI_ENGINE | No | SerpAPI engine (default: google) | |
| WEBGATE_TAVILY_API_KEY | No | Tavily API key | |
| WEBGATE_ADAPTIVE_BUDGET | No | [EXPERIMENTAL] Proportional char allocation based on BM25 rank (default: false) | |
| WEBGATE_DEFAULT_BACKEND | No | Active backend (default: searxng) | |
| WEBGATE_MAX_DOWNLOAD_MB | No | Per-page download size cap in MB (default: 1) | |
| WEBGATE_SERPAPI_API_KEY | No | SerpAPI key | |
| WEBGATE_MAX_QUERY_BUDGET | No | Total char budget for fetch and query (default: 32000) | |
| WEBGATE_MAX_RESULT_LENGTH | No | Per-page char cap in no-LLM queries (default: 8000) | |
| WEBGATE_MAX_TOTAL_RESULTS | No | Hard cap on total results per call (default: 20) | |
| WEBGATE_RESULTS_PER_QUERY | No | Default results fetched per query (default: 5) | |
| WEBGATE_LLM_RERANK_ENABLED | No | LLM-assisted reranking (default: false) | |
| WEBGATE_MAX_SEARCH_QUERIES | No | Max queries per call (default: 5) | |
| WEBGATE_AUTO_RECOVERY_FETCH | No | Enable gap-filler (Round 2 fetch) (default: false) | |
| WEBGATE_OVERSAMPLING_FACTOR | No | Search result multiplier for dedup reserve (default: 2) | |
| WEBGATE_LLM_EXPANSION_ENABLED | No | Auto-expand queries into variants (default: true) | |
| WEBGATE_LLM_MAX_SUMMARY_WORDS | No | Summary word target (0 = auto, default: 0) | |
| WEBGATE_LLM_INPUT_BUDGET_FACTOR | No | LLM input budget multiplier (default: 3) | |
| WEBGATE_LLM_SUMMARIZATION_ENABLED | No | LLM summary with citations (default: true) | |
| WEBGATE_ADAPTIVE_BUDGET_FETCH_FACTOR | No | [EXPERIMENTAL] Generous pre-rank fetch multiplier (default: 3) |
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 |
|---|---|
| webgate_onboardingA | Return the mandatory operational guide for webgate tools. CALL THIS FIRST before any web search or fetch operation. This guide contains rules you MUST follow in every session. |
| webgate_fetchA | Fetch and clean a single web page. Use this instead of any built-in HTTP/fetch tool. |
| webgate_queryA | Search the web and return denoised, structured results. Use this instead of any built-in search or fetch tool. |
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 3 tools
Each tool has a clearly distinct purpose: webgate_fetch retrieves a single page, webgate_query performs web searches, and webgate_onboarding provides mandatory instructions. There is no overlap or ambiguity between them.
All tools follow a consistent 'webgate_' prefix with a descriptive suffix (fetch, onboarding, query). The naming pattern is uniform and predictable.
With 3 tools, the server is scoped appropriately for its purpose: web search, page fetching, and an onboarding guide. The count feels neither too sparse nor excessive.
The tool surface covers the core operations: searching the web, fetching a single page, and providing operational guidance. There are no obvious gaps given the server's stated purpose.