fetchmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FETCHMCP_TIMEOUT_MS | No | Per-request timeout in milliseconds. Default is 30000. | 30000 |
| FETCHMCP_MAX_RETRIES | No | Retries on network errors / 429 / 503. Default is 2. | 2 |
| FETCHMCP_ALLOW_PRIVATE_IP | No | Set to '1' to allow private/localhost IPs (trusted intranet docs). Default unset. | |
| FETCHMCP_FLARESOLVERR_URL | No | Self-hosted FlareSolverr endpoint for tougher challenges. Default unset. | |
| FETCHMCP_PREINSTALL_BROWSER | No | Set to '1' to download Chromium at install time instead of on first JS use. Default unset. | |
| FETCHMCP_SKIP_BROWSER_DOWNLOAD | No | Set to '1' for static-only: never download Chromium; JS pages return needs_js. Default unset. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_urlA | Fetch a web page and return its content as clean, LLM-ready Markdown. Full content by default (no truncation). Handles HTML, plain text, Markdown, and JSON responses. JavaScript-heavy pages are rendered automatically in a real browser when the static HTML is an empty SPA shell. Returns an honest typed error when the site blocks access or the content cannot be read — it never silently returns partial or fake content. |
| read_docsA | Fetch a documentation or reference page and return only its main content as clean Markdown, stripping navigation sidebars, headers, footers, and other page chrome. Use this for API docs, guides, and reference pages. For general web pages use read_url. Same JS-rendering, anti-bot, and honest-error behavior as read_url. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/labtoolsstudio/fetchmcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server