web-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB_MCP_USER_AGENT | No | User-Agent header for static fetch | LocalLLM-WebMCP/0.1 |
| WEB_MCP_SERVER_NAME | No | MCP server name | web-mcp |
| WEB_MCP_DEFAULT_RENDER | No | Default render mode | auto |
| WEB_MCP_FETCH_TIMEOUT_MS | No | Timeout for static fetch in milliseconds | 15000 |
| WEB_MCP_DEFAULT_MAX_CHARS | No | Default maximum characters for web_fetch | 20000 |
| WEB_MCP_BROWSER_TIMEOUT_MS | No | Timeout for browser fetch in milliseconds | 20000 |
| WEB_MCP_DEFAULT_MAX_RESULTS | No | Default number of results for web_search | 10 |
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_searchB | Search the web and return a list of candidate pages. This scaffold returns mock results only. |
| web_fetchC | Fetch a URL with static HTTP and return readable Markdown-style page text. |
| web_findC | Fetch a URL with static HTTP and find text within the extracted page text. |
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
web_fetch and web_find both involve fetching a URL, but one returns the full page text and the other finds specific text within it, making their purposes distinct with clear descriptions. web_search is entirely different.
All tools follow the consistent 'web_verb' pattern (fetch, find, search), indicating a predictable naming convention.
Three tools is an appropriate number for a web utility server, covering core operations without being too sparse or excessive.
The tools cover basic web tasks (fetch, find text, search) but lack advanced features like POST requests, pagination, or element extraction, which are notable gaps for a comprehensive web server.