WebFetch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key for accessing Claude |
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 |
|---|---|
| web_fetchA | Fetch a web page and answer questions about its content. Fetches the URL, converts HTML to markdown, and uses Claude to answer the prompt based on the page content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| webfetch_skill | How to effectively use WebFetch: prompt tips, URL handling, caching, limitations. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name 'web_fetch' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
The server has only one tool, which is at the low end of the range. While it covers the core function, more tools (e.g., for raw content or separate fetch and ask) could be expected.
The tool combines fetching and Q&A, covering the stated purpose well. However, it lacks flexibility for users who want only the raw page content or to customize fetching options.