mcp-server-fetch-python

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-server-fetch-python?

The mcp-server-fetch-python is a server designed for fetching and transforming web content into various formats, providing tools for extracting content from web pages, including support for JavaScript-rendered content and media files.

how to use mcp-server-fetch-python?

To use the server, you can either configure it with Claude Desktop or install it locally. For Claude Desktop, add the server configuration to the appropriate config file. For local installation, clone the repository and run the server using the provided commands.

key features of mcp-server-fetch-python?

  • get-raw-text: Extracts raw text content from URLs without rendering.
  • get-rendered-html: Fetches fully rendered HTML using a headless browser.
  • get-markdown: Converts web page content to Markdown format.
  • get-markdown-from-media: AI-powered content extraction from media files using computer vision and OCR.

use cases of mcp-server-fetch-python?

  1. Extracting structured data from web pages.
  2. Fetching content from modern web applications that require JavaScript rendering.
  3. Converting web content into Markdown for documentation purposes.
  4. Analyzing visual content from images and videos.

FAQ from mcp-server-fetch-python?

  • What is required to use the AI-powered media extraction tool?

You need to set the OPENAI_API_KEY in your environment variables.

  • Can I run the server locally?

Yes, you can clone the repository and run it locally using the provided commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

2 hours ago
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