Skrape MCP Server

Created By
skrapeaia year ago
MCP Server for skrape.ai, lets you input any URL and it returns clean markdown for the LLM
Overview

What is Skrape MCP Server?

Skrape MCP Server is a tool that converts any webpage into clean, LLM-ready Markdown format, making it ideal for integrating web content into language models like Claude and GPT.

How to use Skrape MCP Server?

To use the Skrape MCP Server, input any URL into the server, and it will return a structured Markdown output. You can install it via Smithery or manually configure it with your API key.

Key features of Skrape MCP Server?

  • Converts web pages to clean, structured Markdown
  • Removes ads and irrelevant content for clarity
  • Supports JavaScript rendering for dynamic content
  • Provides an optional JSON response format for advanced integrations

Use cases of Skrape MCP Server?

  1. Feeding web content into LLMs for processing
  2. Generating structured documentation from web pages
  3. Simplifying the integration of web data into applications

FAQ from Skrape MCP Server?

  • Can Skrape MCP Server handle all types of web pages?

Yes! It can convert any webpage into Markdown, regardless of its structure.

  • Is there a cost associated with using Skrape MCP Server?

The server is free to use, but you need an API key from skrape.ai.

  • How does Skrape MCP Server ensure clean output?

It automatically removes unnecessary elements like ads and menus, focusing on the main content.

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