Skip to main content
Glama

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.

CAUTION

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 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)

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

  1. Clone or download the source code:

    git clone https://github.com/LangGPT/mcp-fetch.git
    cd mcp-fetch
  2. Install dependencies using uv:

    uv sync
  3. Test the server:

    uv run python -m mcp_fetch --help

Using with Claude Desktop (Local Source)

  1. Create Claude Desktop configuration:

    {
      "mcpServers": {
        "mcp-fetch": {
          "command": "uv",
          "args": [
            "run",
            "--directory",
            "/path/to/your/mcp-fetch",
            "python",
            "-m",
            "mcp_fetch"
          ]
        }
      }
    }
  2. Add configuration to Claude Desktop:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%/Claude/claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json

  3. 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

When using uv no specific installation is needed. We will use uvx to directly run mcp-fetch:

uvx mcp-fetch

Using pip

pip install mcp-fetch

After installation, run it as:

python -m mcp_fetch

Package 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

  1. Install development dependencies:

    uv sync --dev
  2. Run linting and type checking:

    uv run ruff check
    uv run pyright
  3. Build the package:

    uv build

Testing

Test the server locally:

uv run python -m mcp_fetch

Use the MCP inspector for debugging:

npx @modelcontextprotocol/inspector uv run python -m mcp_fetch

Making Changes

  1. Edit the source code in src/mcp_fetch/

  2. Test your changes with uv run python -m mcp_fetch

  3. Update version in pyproject.toml if needed

  4. Run tests and linting

Publishing

Publishing to PyPI

  1. Build the package:

    uv build
  2. Publish to PyPI:

    uv publish

    Or using twine:

    pip install twine
    twine upload dist/*

Publishing to GitHub

  1. Initialize git repository (if not already done):

    git init
    git branch -m main
  2. Add and commit files:

    git add .
    git commit -m "Initial commit: MCP Web Fetch server without robots.txt checking"
  3. 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 main
  4. Create a release on GitHub:

    • Go to your repository on GitHub

    • Click "Releases" → "Create a new release"

    • Tag version: v0.6.3

    • Release title: v0.6.3 - MCP Fetch

    • Describe 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:latest

Customization

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_fetch

For uvx installations:

npx @modelcontextprotocol/inspector uvx mcp-fetch

Contributing

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 tool
fetchB

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL to fetch
max_lengthNoMaximum number of characters to return.
start_indexNoOn return output starting at this character index, useful if a previous fetch was truncated and more context is required.
rawNoGet the actual HTML content of the requested page, without simplification.

TDQS

B3.3/5.0
Behavior3/5

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.

Conciseness3/5

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.

Completeness3/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines3/5

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

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'fetch' has a clear and distinct purpose.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive
ResponsivenessNo issues

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

Related MCP Servers

Latest Blog Posts

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