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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aza-ali/turbowebfetch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server