A Model Context Protocol (MCP) server that fetches web pages and extracts content using CSS selectors or returns full page HTML, title, and metadata.
Overview
The Web Scraper MCP Server provides simple, no-auth web content extraction:
Fetch any public web page and return its full HTML, title, and meta description
Target specific elements on a page using CSS selectors
Works with any public HTTP/HTTPS URL — no API key or credentials required
Perfect for:
AI assistants that need to read live content from any public web page
Extracting specific elements like articles, tables, or product listings
Quick page lookups without setting up a full scraping pipeline
Tools
Fetches a web page and returns either the full page content or elements matching a CSS selector.
Inputs:
- `url` (string, required) — Fully qualified HTTP/HTTPS URL to fetch- `selector` (string, optional) — CSS selector to target specific elements on the page
output (without selector):
{ "url": "https://example.com", "title": "Example Domain", "description": "Meta description of the page", "html": "<!DOCTYPE html>..."}
output (with selector):
{ "url": "https://example.com", "data": [ "<h1>Example Domain</h1>", "<p>This domain is for use in illustrative examples.</p>" ]}
API Parameters Reference
Use standard CSS selectors to target elements on the page:
h1 — All <h1> headingsarticle p — All <p> inside <article> tags.product-title — Elements with class "product-title"#main-content — Element with ID "main-content"table tr — All table rowsmeta[name="author"] — Meta tags with name="author"
when selector is provided, the tool returns a list of matching element HTML strings. When omitted, the full raw page HTML is returned.
Must be a fully qualified URL including the scheme: https://example.com, not example.com
Must be a publicly accessible HTTP/HTTPS endpoint
Pages behind login walls or paywalls will not return protected content
Request timeout is 10 seconds — very slow pages may fail
Troubleshooting
Cause: API key not provided in request headers or incorrect format
Solution:
Verify Authorization: Bearer YOUR_API_KEY and X-Mewcp-Credential-Id: CREDENTIAL-ID headers are present
Check the credential is active in your MewCP account
Cause: API calls have exceeded your request limits
Solution:
Check credit usage in your Curious Layer dashboard
Upgrade to a paid plan or add credits for higher limits
Contact support for credit adjustments
Cause: JSON payload is invalid or missing required fields
Solution:
Validate JSON syntax before sending
Ensure the url parameter is a fully qualified HTTP/HTTPS URL
