mult-fetch-mcp-server

Created By
lmcc-deva year ago
A versatile MCP-compliant web content fetching tool that supports multiple modes (browser/node), formats (HTML/JSON/Markdown/Text), and intelligent proxy detection, with bilingual interface (English/Chinese).
Overview

What is Mult Fetch Mcp Server?

Mult Fetch Mcp Server is a versatile MCP-compliant web content fetching tool that supports multiple modes (browser/node), formats (HTML/JSON/Markdown/Text), and intelligent proxy detection, with a bilingual interface (English/Chinese).

How to use Mult Fetch Mcp Server?

To use the server, install it via npm or Smithery, configure it according to your environment, and then run it to fetch web content using various commands.

Key features of Mult Fetch Mcp Server?

  • Supports multiple fetching modes: browser and Node.js.
  • Fetches content in various formats: HTML, JSON, Markdown, and plain text.
  • Intelligent proxy detection and bilingual support.
  • Modular design for easy maintenance and extension.

Use cases of Mult Fetch Mcp Server?

  1. Web scraping for data extraction.
  2. Fetching content for AI assistants.
  3. Integrating with applications that require web content.

FAQ from Mult Fetch Mcp Server?

  • Can I use it without installation?

Yes! You can run it directly using npx without installation.

  • Is it available in multiple languages?

Yes! It supports both English and Chinese.

  • How do I configure proxy settings?

You can specify proxy settings in the request parameters or use environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lmcc-dev
Star
2
Language
TypeScript
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