weblens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSECURE_TLS | No | Set to '1' to accept self-signed certificates. | 0 |
| CHROMIUM_PATH | No | Override the browser. By default WebLens uses Playwright's bundled Chromium; set this to use a specific Chrome/Chromium/Edge executable. |
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 |
|---|---|
| fetch_pageA | Fetch and render a web page. Returns the absolute path to a local markdown file containing the page content with downloaded images embedded as local file paths. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose is clearly stated and unambiguous.
The tool name 'fetch_page' follows a clear snake_case verb_noun pattern. With only one tool, there is no inconsistency.
A single tool feels thin, especially for a server named 'weblens' which implies a boader web toolkit. However, as a focused page-fetching utility, the count is borderline rather than clearly insufficient.
The core operation of fetching and rendering a web page to a local markup file is fully covered. Minor gaps exist like lack of options for custom headers or alternative output formats, but no critical lifecycle is missing for this narrow domain.