Fetch MCP Server
# Fetch MCP Server
A Model Context Protocol server that provides web content fetching capabilities. This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
The fetch tool will truncate the response, but by using the `start_index` argument, you can specify where to start the content extraction. This lets models read a webpage in chunks, until they find the information they need.
### Available Tools
- `fetch` - Fetches a URL from the internet and extracts its contents as markdown.
- `url` (string, required): URL to fetch
- `max_length` (integer, optional): Maximum number of characters to return (default: 5000)
- `start_index` (integer, optional): Start content from this character index (default: 0)
- `raw` (boolean, optional): Get raw content without markdown conversion (default: false)
### Prompts
- **fetch**
- Fetch a URL and extract its contents as markdown
- Arguments:
- `url` (string, required): URL to fetch
## Installation
Optionally: Install node.js, this will cause the fetch server to use a different HTML simplifier that is more robust.
### Using uv (recommended)
When using [`uv`](https://docs.astral.sh/uv/) no specific installation is needed. We will
use [`uvx`](https://docs.astral.sh/uv/guides/tools/) to directly run `mcp-server-fetch`.
### Using PIP
Alternatively you can install `mcp-server-fetch` via pip:
```
pip install mcp-server-fetch
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool has a single, clearly defined purpose of fetching URLs and optionally extracting markdown content.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'fetch' is simple, descriptive, and follows a clear verb-based pattern appropriate for its function.
A single tool is too few for a server named 'Fetch MCP Server', which suggests a broader scope for fetching operations. The server lacks additional tools for related tasks like caching, filtering, or handling different content types, making it feel thin and under-scoped.
The tool surface is severely incomplete for a fetching domain. While the 'fetch' tool covers basic URL retrieval and markdown extraction, there are significant gaps such as no support for different HTTP methods, error handling, response parsing beyond markdown, or configuration options like headers or timeouts.