Web Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_DIR | No | Cache directory | ./cache |
| PROXY_URL | No | Proxy endpoint; empty string disables proxying | http://127.0.0.1:7890 |
| CACHE_DISABLED | No | Set to 1 to disable result caching | 0 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web across engines. Auto-selects CN or international engines based on the query language; international engines route through the configured proxy. Use engine='all' to fan out across every engine, or specify one (duckduckgo|bing|bingcn|baidu|sogou|so). |
| fetch_urlA | Fetch a URL, strip boilerplate, and return the page content as markdown. International hosts auto-route through the configured proxy; CN hosts (baidu/bing.cn/so/...) go direct. |
| deep_researchA | Multi-engine deep research: fan out across engines (auto-selects CN vs international), dedupe + rank results, fetch the top pages, and synthesize a cited markdown report. Use for thorough, multi-source research. |
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: web_search for searching, fetch_url for fetching a specific page, and deep_research for multi-step synthesis. While deep_research uses search, it is clearly a higher-level workflow, so no ambiguity.
web_search and fetch_url follow a consistent verb_noun pattern, but deep_research uses an adjective_noun pattern. All names use lowercase and underscores, so the deviation is minor and does not hinder readability.
Three tools is well-scoped for a web search server: search, fetch, and deep research cover the core needs without redundancy or bloat.
The surface covers the essential operations of searching, fetching, and synthesizing. Minor gaps exist (e.g., no tool for image search or specific engine metadata), but they are not critical for typical use.