web-to-markdown-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_url_as_markdownA | Fetch a URL and return the main content as Markdown. First tries a plain HTTP request with an Accept: text/markdown header. If the server responds with Content-Type: text/markdown (e.g. Cloudflare Markdown for Agents sites), the body is returned immediately without launching a browser. Otherwise, uses patchright (a Playwright fork with anti-detection patches) to drive real Chromium, which clears most Cloudflare bot challenges and renders JavaScript-required pages. A single headless Chromium instance is kept alive across calls so subsequent fetches avoid the browser cold-start cost (~2-5s). After navigation, polls the page DOM and runs trafilatura, returning as soon as the extracted Markdown stabilizes across two consecutive polls — typically within a few hundred milliseconds of the DOM being built, regardless of whether trackers, ads, and analytics are still loading in the background. |
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 confusion between tools.
The single tool is named clearly with a verb_noun pattern (fetch_url_as_markdown), which is descriptive and consistent.
One tool is appropriate for this focused server's purpose; it encapsulates all necessary functionality for fetching a URL and converting it to markdown.
The tool fully covers the server's domain by handling both simple HTTP and JavaScript-heavy pages, returning markdown content without obvious gaps.