MCP Fetch
MCP Fetch enables web content retrieval with unrestricted access (robots.txt checking removed), converting HTML to markdown for LLM consumption.
Capabilities:
Fetch web content from any URL, bypassing robots.txt restrictions
Convert HTML to markdown automatically for easier LLM processing
Retrieve raw HTML using the
rawparameter when neededRead pages in chunks via
start_indexfor handling large contentControl response length with
max_length(default 5000, up to 1,000,000 characters)Access local/internal IP addresses (note: security risk)
Custom user-agent configuration for web requests
Proxy support via
--proxy-urlargumentIntegration with Claude Desktop and VS Code as an MCP server
⚠️ Security Warning: Ignores robots.txt restrictions and can access internal addresses, potentially violating website policies and exposing sensitive data.
Supports containerization with Docker, including instructions for building, tagging, and pushing Docker images
Enables publishing the MCP server to GitHub, with specific instructions for repository setup and release creation
Allows publishing the package to PyPI for easier installation via package managers
Click on "Install 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., "@MCP Fetchfetch the latest tech news from Hacker News homepage"
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.
MCP Fetch
A Model Context Protocol server that provides web content fetching capabilities with robots.txt checking removed. This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
This is a modified version of the original mcp-server-fetch that removes all robots.txt checking, allowing unrestricted access to web content.
This server can access local/internal IP addresses and may represent a security risk. Exercise caution when using this MCP server to ensure this does not expose any sensitive data. Additionally, this version ignores robots.txt restrictions which may violate some websites' access policies.
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 fetchmax_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)
Related MCP server: MCP URL Fetcher
Available Prompts
fetch
Fetch a URL and extract its contents as markdown
Arguments:
url(string, required): URL to fetch
Installation and Usage
Local Development Setup
Clone or download the source code:
git clone https://github.com/LangGPT/mcp-fetch.git cd mcp-fetchInstall dependencies using uv:
uv syncTest the server:
uv run python -m mcp_fetch --help
Using with Claude Desktop (Local Source)
Create Claude Desktop configuration:
{ "mcpServers": { "mcp-fetch": { "command": "uv", "args": [ "run", "--directory", "/path/to/your/mcp-fetch", "python", "-m", "mcp_fetch" ] } } }Add configuration to Claude Desktop:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%/Claude/claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Restart Claude Desktop to load the new server.
Using with VS Code (Local Source)
Add to your VS Code settings or .vscode/mcp.json:
{
"mcp": {
"servers": {
"mcp-fetch": {
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/your/mcp-fetch",
"python",
"-m",
"mcp_fetch"
]
}
}
}
}Installation via Package Manager
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run mcp-fetch:
uvx mcp-fetchUsing pip
pip install mcp-fetchAfter installation, run it as:
python -m mcp_fetchPackage Manager Configuration
Claude Desktop with uvx
{
"mcpServers": {
"mcp-fetch": {
"command": "uvx",
"args": ["mcp-fetch"]
}
}
}VS Code with uvx
{
"mcp": {
"servers": {
"mcp-fetch": {
"command": "uvx",
"args": ["mcp-fetch"]
}
}
}
}Development
Setting up Development Environment
Install development dependencies:
uv sync --devRun linting and type checking:
uv run ruff check uv run pyrightBuild the package:
uv build
Testing
Test the server locally:
uv run python -m mcp_fetchUse the MCP inspector for debugging:
npx @modelcontextprotocol/inspector uv run python -m mcp_fetchMaking Changes
Edit the source code in
src/mcp_fetch/Test your changes with
uv run python -m mcp_fetchUpdate version in
pyproject.tomlif neededRun tests and linting
Publishing
Publishing to PyPI
Build the package:
uv buildPublish to PyPI:
uv publishOr using twine:
pip install twine twine upload dist/*
Publishing to GitHub
Initialize git repository (if not already done):
git init git branch -m mainAdd and commit files:
git add . git commit -m "Initial commit: MCP Web Fetch server without robots.txt checking"Create GitHub repository and push:
# Create repository on GitHub first, then: git remote add origin https://github.com/LangGPT/mcp-fetch.git git push -u origin mainCreate a release on GitHub:
Go to your repository on GitHub
Click "Releases" → "Create a new release"
Tag version:
v0.6.3Release title:
v0.6.3 - MCP FetchDescribe your changes
Publish release
Building Docker Image
docker build -t mcp-fetch .
docker tag mcp-fetch LangGPT/mcp-fetch:latest
docker push LangGPT/mcp-fetch:latestCustomization
robots.txt
This version has robots.txt checking completely removed. All web requests will proceed regardless of robots.txt restrictions.
User-agent
By default, depending on if the request came from the model (via a tool), or was user initiated (via a prompt), the server will use either the user-agent:
ModelContextProtocol/1.0 (Autonomous; +https://github.com/modelcontextprotocol/servers)or:
ModelContextProtocol/1.0 (User-Specified; +https://github.com/modelcontextprotocol/servers)This can be customized by adding the argument --user-agent=YourUserAgent to the args list in the configuration.
Proxy
The server can be configured to use a proxy by using the --proxy-url argument.
Debugging
You can use the MCP inspector to debug the server:
For local development:
npx @modelcontextprotocol/inspector uv run python -m mcp_fetchFor uvx installations:
npx @modelcontextprotocol/inspector uvx mcp-fetchContributing
We encourage contributions to help expand and improve mcp-fetch. Whether you want to add new tools, enhance existing functionality, or improve documentation, your input is valuable.
License
mcp-fetch is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Available Tools
1 toolfetchB
Fetches a URL from the internet and optionally extracts its contents as markdown.
Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to fetch | |
| max_length | No | Maximum number of characters to return. | |
| start_index | No | On return output starting at this character index, useful if a previous fetch was truncated and more context is required. | |
| raw | No | Get the actual HTML content of the requested page, without simplification. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool enables internet access and can extract markdown, but lacks details on rate limits, authentication needs, error handling, or output format. It adds some behavioral context but misses key operational traits for a fetch tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences but includes redundant context about historical internet access limitations that doesn't directly aid tool selection. It's somewhat front-loaded with the core purpose, but the second sentence could be more concise and focused on tool behavior rather than background.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a fetch tool with 4 parameters, 100% schema coverage, and no output schema, the description is moderately complete. It covers the purpose and internet access context but lacks details on output format, errors, or limitations, which are important given the tool's complexity and lack of annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema fully documents all parameters. The description mentions optional markdown extraction, which loosely relates to the 'raw' parameter, but adds minimal semantic value beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: fetching a URL from the internet and optionally extracting contents as markdown. It specifies the verb ('fetches') and resource ('URL'), though it doesn't distinguish from siblings since none exist. The mention of internet access context is helpful but slightly dilutes the core purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage context by noting that the tool grants internet access where previously unavailable, suggesting it should be used for up-to-date information retrieval. However, it lacks explicit guidance on when to use alternatives (none exist) or any exclusions, leaving usage somewhat open-ended.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'fetch' has a clear and distinct purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'fetch' is straightforward and appropriate.
One tool is too few for most server purposes, as it severely limits functionality and scope. While 'fetch' is useful, a server typically needs more tools to cover a meaningful domain effectively.
The server's purpose appears to be fetching web content, but with only one tool, the surface is severely incomplete. There are obvious gaps, such as no ability to handle errors, cache results, or manage different content types beyond markdown extraction.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
URL to clean markdown for LLMs: a polite, robots.txt-respecting web reader. Free, no API key
A Model Context Protocol server for Wix AI tools
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows LLMs to interact with web content through standardized tools, currently supporting web scraping functionality.1MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to fetch and process web content in multiple formats (HTML, JSON, Markdown, text) with automatic format detection.56
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables LLMs to retrieve web content and save it to local files for permanent storage and later access.12MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that intelligently fetches and processes web content, transforming websites and documentation into clean, structured markdown with nested URL crawling capabilities.2159MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LangGPT/mcp-fetch'
If you have feedback or need assistance with the MCP directory API, please join our Discord server