Fetcher MCP

Created By
jae-jaea year ago
MCP server for fetch web page content using Playwright headless browser.
Overview

what is Fetcher MCP?

Fetcher MCP is a server application designed to fetch web page content using the Playwright headless browser, enabling users to retrieve and process web data efficiently.

how to use Fetcher MCP?

To use Fetcher MCP, you can run it directly with the command npx -y fetcher-mcp. For debugging, use the --debug option to open the browser window.

key features of Fetcher MCP?

  • fetch_url: Retrieve content from a single URL with intelligent extraction and Markdown conversion.
  • fetch_urls: Batch fetch content from multiple URLs in parallel for improved performance.
  • Customizable parameters for timeout, content extraction, and output format.

use cases of Fetcher MCP?

  1. Scraping data from news websites for analysis.
  2. Collecting product information from e-commerce sites.
  3. Aggregating content from multiple blogs for research purposes.

FAQ from Fetcher MCP?

  • Can Fetcher MCP handle JavaScript-heavy websites?

Yes! Fetcher MCP uses Playwright, which can render JavaScript content.

  • Is there a limit to the number of URLs I can fetch?

No, you can fetch multiple URLs in parallel, but performance may vary based on the number of requests.

  • How do I configure the MCP server?

You can configure it in the Claude Desktop application by editing the claude_desktop_config.json file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jae-jae
Star
709
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago