Fetch MCP Server with CSS selectors function

Created By
burnworksa year ago
Overview

What is Fetch MCP Server?

Fetch MCP Server is a Model Context Protocol server designed to fetch web content using CSS selectors, enabling LLMs to retrieve and process information from web pages by converting HTML to markdown for easier consumption.

How to use Fetch MCP Server?

To use the Fetch MCP Server, you can either install it via pip or use it with uv. After installation, you can run it as a script or configure it for specific applications by setting up commands in your environment.

Key features of Fetch MCP Server?

  • Fetches web content and converts it to markdown format.
  • Supports CSS selectors for targeted content extraction.
  • Allows customization of user-agent and proxy settings.
  • Provides debugging tools for server inspection.

Use cases of Fetch MCP Server?

  1. Extracting main article content from news websites.
  2. Focusing on specific sections of documentation pages.
  3. Targeting precise content from large web pages for data analysis.

FAQ from Fetch MCP Server?

  • Can I extract content from any website?

Yes, as long as the website allows it and you comply with its robots.txt file.

  • Is there a limit to the amount of content I can fetch?

Yes, you can specify a maximum length for the content returned.

  • How do I customize the server settings?

You can customize settings like user-agent and proxy by adding arguments in the configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
burnworks
Star
0
Language
Python
License
MIT license

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)

a day ago