turbowebfetch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TURBOFETCH_HEADLESS | No | Headless mode (auto-switches if blocked) | true |
| TURBOFETCH_HUMAN_MODE | No | Human-like scrolling/delays | true |
| TURBOFETCH_MAX_PROCESSES | No | Max concurrent browsers | 14 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Fetch and render a web page using a real Chrome browser. Handles JavaScript-heavy sites, anti-bot protection, and dynamic content. Auto-detects when content has loaded by monitoring DOM changes and network activity. |
| fetch_batchA | Fetch multiple URLs in parallel using real Chrome browsers. Each URL gets its own browser instance for isolation. Auto-detects content stabilization. Returns results in same order as input URLs. |
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 2 tools
The two tools have clearly distinct purposes: one fetches a single URL, the other fetches multiple URLs in parallel. Descriptions explicitly highlight the difference in scope and isolation, leaving no ambiguity.
Both tool names follow the consistent pattern 'fetch' for single and 'fetch_batch' for batch, using a suffix to indicate the variant. No mixing of styles or conventions.
With only 2 tools, the server is minimal but still covers the basic use cases of single and batch web fetching. The scope is narrow but appropriate for a focused web fetching server, though a few more tools (e.g., with options) could be justified.
The server covers the core functionality of fetching and rendering web pages, but lacks advanced features like custom headers, cookies, or wait conditions. Users needing fine-grained control may find the surface incomplete, though basic needs are met.