Web Fetch MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_webpageA | Fetches the raw HTML content of a webpage from the given URL |
| fetch_webpage_textA | Fetches a webpage and extracts clean text content without HTML tags |
| fetch_webpage_markdownA | Fetches a webpage and converts it to markdown format |
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 3 tools
Each tool targets a distinct output format (raw HTML, plain text, markdown), so there is no ambiguity about which tool to use. The descriptions clearly differentiate the three fetch modes.
All tools follow a consistent pattern: fetch_webpage for raw HTML, fetch_webpage_text for text, and fetch_webpage_markdown for markdown. The suffix clearly indicates the output format, making the naming predictable.
Three tools is well-scoped for a web fetching server, covering the three most common content formats without unnecessary redundancy. This is within the ideal range for a focused utility.
For the stated purpose of fetching webpages, the server covers raw HTML, clean text, and markdown, which are the primary output formats needed. There are no obvious missing operations for basic web content retrieval.