Skip to main content
Glama
Skrape MCP Server

Skrape MCP Server

Official
by skrapeai

Skrape MCP Server

Convert webpages into clean, LLM-ready Markdown using skrape.ai. An MCP server that seamlessly integrates web scraping with Claude Desktop and other MCP-compatible applications.

Key Features

  • Clean Output: Removes ads, navigation, and irrelevant content

  • JavaScript Support: Handles dynamic content rendering

  • LLM-Optimized: Structured Markdown perfect for AI consumption

  • Consistent Format: Uniform structure regardless of source

Related MCP server: Scraper MCP

Features

Tools

  • get_markdown - Convert any webpage to LLM-ready Markdown

    • Takes any input URL and optional parameters

    • Returns clean, structured Markdown optimized for LLM consumption

    • Supports JavaScript rendering for dynamic content

    • Optional JSON response format for advanced integrations

Installation

Installing via Smithery

To install Skrape MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @skrapeai/skrape-mcp --client claude

Manual Installation

  1. Get your API key from skrape.ai

  2. Install dependencies:

npm install
  1. Build the server:

npm run build
  1. Add the server config to Claude Desktop:

On MacOS:

nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows:

notepad %APPDATA%/Claude/claude_desktop_config.json

Add this configuration (replace paths and API key with your values):

{
  "mcpServers": {
    "skrape": {
      "command": "node",
      "args": ["path/to/skrape-mcp/build/index.js"],
      "env": {
        "SKRAPE_API_KEY": "your-key-here"
      }
    }
  }
}

Using with LLMs

Here's how to use the server with Claude or other LLM models:

  1. First, ensure the server is properly configured in your LLM application

  2. Then, you can ask the ALLMI to fetch and process any webpage:

Convert this webpage to markdown: https://example.com

Claude will use the MCP tool like this:
<use_mcp_tool>
<server_name>skrape</server_name>
<tool_name>get_markdown</tool_name>
<arguments>
{
  "url": "https://example.com",
  "options": {
    "renderJs": true
  }
}
</arguments>
</use_mcp_tool>

The resulting Markdown will be clean, structured, and ready for LLM processing.

Advanced Options

The get_markdown tool accepts these parameters:

  • url (required): Any webpage URL to convert

  • returnJson (optional): Set to true to get the full JSON response instead of just markdown

  • options (optional): Additional scraping options

    • renderJs: Whether to render JavaScript before scraping (default: true)

Example with all options:

<use_mcp_tool>
<server_name>skrape</server_name>
<tool_name>get_markdown</tool_name>
<arguments>
{
  "url": "https://example.com",
  "returnJson": true,
  "options": {
    "renderJs": false
  }
}
</arguments>
</use_mcp_tool>

Development

For development with auto-rebuild:

npm run watch

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.


Available Tools

1 tool
get_markdownC

Get markdown content from a webpage using skrape.ai

Inputs: url (required), returnJson, options.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or confusion between tools. The tool's purpose is clearly defined as retrieving markdown content from webpages, making it distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_markdown' follows a clear verb_noun pattern, which would be consistent if more tools were added.

    Tool Count2/5

    A single tool is too few for a server named 'Skrape MCP Server', which suggests a broader scraping or data extraction purpose. This minimal toolset limits functionality and feels incomplete for the implied scope, as it only handles markdown retrieval without other common scraping operations.

    Completeness1/5

    The server is severely incomplete for a scraping domain. It lacks basic operations such as fetching HTML, extracting specific elements, handling different content types, or managing sessions. With only one tool for markdown, agents will face dead ends when trying to perform typical scraping tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
      26
      1
      217,624 PyPI
      91,952
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A context-optimized web scraping server that converts HTML to markdown/text and applies CSS selectors server-side, reducing token usage by 70-90% while providing AI tools with clean, filtered web content.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A server that extracts clean Markdown from web pages using headless Chrome, reducing token usage by up to 90% for AI tools like Claude.
      11 npm
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
      MIT