Fetch

Created By
testa year ago
Web content fetching and conversion for efficient LLM usage
Overview

What is Fetch?

Fetch is a Model Context Protocol (MCP) server designed for web content fetching and conversion, allowing Large Language Models (LLMs) to retrieve and process content from web pages by converting HTML into markdown for easier consumption.

How to use Fetch?

To use Fetch, install it via node.js or pip, and then run the server using the command: python -m mcp_server_fetch or with uvx as specified in the documentation. You can fetch content by calling the fetch tool with a URL.

Key features of Fetch?

  • Fetches web URLs and extracts their content in markdown format.
  • Supports configuration options such as maximum length of content and starting index for extraction.
  • Customizable user-agent and robots.txt compliance settings.

Use cases of Fetch?

  1. Enabling LLMs to access and process data from web pages for various applications.
  2. Converting online articles into a simplified format for analysis.
  3. Assisting in data retrieval tasks for research and data aggregation workflows.

FAQ from Fetch?

  • Can Fetch handle all types of web content?

Fetch is capable of extracting content from most web pages, although results may vary based on the site's structure and restrictions.

  • Is Fetch easy to integrate with other tools?

Yes! Fetch is designed to integrate smoothly with LLMs and can be customized to meet specific needs.

  • Is there any usage limit for Fetch?

Fetch does not impose strict usage limits, but your implementation may be subject to the guidelines of the websites you access.

Server Config

{
  "mcpServers": {
    "fetch": {
      "args": [
        "mcp-server-fetch"
      ],
      "command": "uvx"
    }
  }
}
Project Info
Hosted
Featured
Created At
a year ago
Updated At
8 months ago
Author Name
test
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago
Alloy

2 days ago