Web Fetch MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Web Fetch MCP Server convert https://example.com to markdown"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Web Fetch MCP Server
A Model Context Protocol (MCP) server that enables LLMs to fetch and process web page contents. This server provides tools for retrieving raw HTML, extracting clean text, and converting web pages to markdown format.
Features
fetch_webpage: Retrieves raw HTML content from any URL
fetch_webpage_text: Extracts clean text content without HTML tags
fetch_webpage_markdown: Converts web pages to markdown format
Related MCP server: Fetch MCP Server
Installation
Install dependencies:
npm installBuild the project:
npm run buildUsage with LM Studio
To use this MCP server with LM Studio, you need to configure it in your MCP settings.
Configuration
Add the following to your LM Studio MCP configuration file (typically located at ~/.lmstudio/mcp-settings.json or similar):
{
"mcpServers": {
"web-fetch": {
"command": "node",
"args": ["D:\\Projects\\web search mcp\\dist\\index.js"]
}
}
}Adjust the path to match your actual installation directory.
Alternative: Global Installation
You can also install the server globally or use npx:
npm install -g .Then configure LM Studio to use:
{
"mcpServers": {
"web-fetch": {
"command": "web-fetch-mcp"
}
}
}Available Tools
1. fetch_webpage
Fetches the raw HTML content of a webpage.
Input:
url(string, required): The URL of the webpage to fetch
Example:
{
"url": "https://example.com"
}2. fetch_webpage_text
Fetches a webpage and extracts clean text content without HTML tags, scripts, or styles.
Input:
url(string, required): The URL of the webpage to fetch
Example:
{
"url": "https://example.com"
}3. fetch_webpage_markdown
Fetches a webpage and converts it to markdown format, preserving structure like headings, links, and lists.
Input:
url(string, required): The URL of the webpage to fetch
Example:
{
"url": "https://example.com"
}Development
Build
npm run buildWatch mode (auto-rebuild on changes)
npm run devRun directly
npm startTechnical Details
Protocol: Model Context Protocol (MCP) via stdio transport
HTTP Client: Axios with 30-second timeout and automatic redirect handling
HTML Parsing: Cheerio for efficient HTML parsing
Markdown Conversion: Turndown for high-quality HTML to Markdown conversion
User Agent: Mimics modern browser to avoid bot detection
Error Handling
The server includes comprehensive error handling for:
Network failures
Invalid URLs
Timeout errors
HTTP errors (404, 500, etc.)
Errors are returned in a structured format with descriptive messages.
Security Notes
The server fetches content from any URL provided
Be cautious when fetching content from untrusted sources
Consider implementing URL allowlists for production use
The server respects redirects (max 5)
License
MIT
Available Tools
3 toolsfetch_webpageA
Fetches the raw HTML content of a webpage from the given URL
Inputs: url (required).
fetch_webpage_markdownA
Fetches a webpage and converts it to markdown format
Inputs: url (required).
fetch_webpage_textA
Fetches a webpage and extracts clean text content without HTML tags
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Web tools for AI agents: URL to clean Markdown, site crawl, screenshots, PDF/Office to text, OCR.
Web data for agents. Extract web pages, crawl websites, discover URLs, and search the web.
Turn any web page URL or HTML into clean Markdown or plain text for an LLM to read.
Read a URL as clean markdown, screenshot a website, url to PDF. Web access for agents, no signup.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables retrieval and processing of web page content for LLMs by converting HTML to markdown, with support for content truncation and pagination.13MIT
- AlicenseBqualityDmaintenanceEnables LLMs to retrieve and process web content by fetching URLs and converting HTML to markdown format. Supports chunked reading of large pages and can access both public websites and local networks.1MIT
- AlicenseCqualityFmaintenanceEnables LLMs to retrieve and process web content by fetching URLs and converting HTML to markdown, with support for chunked reading and customizable user-agents.1MIT
- AlicenseAqualityDmaintenanceEnables LLMs to fetch and process web content by converting HTML into markdown for easier consumption. It supports chunked reading via pagination and provides configuration options for robots.txt compliance and proxy usage.1MIT