Skip to main content
Glama
enesjakozh
skrapeai

Skrape MCP Server

Official
by skrapeai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor MCP de Skrape

insignia de herrería Convierte cualquier página web en Markdown limpio y compatible con LLM con skrape.ai . Perfecto para alimentar contenido web a LLM.

Este servidor MCP proporciona una interfaz sencilla para convertir páginas web a formato Markdown estructurado y limpio mediante la API de skrape.ai. Está diseñado para funcionar a la perfección con Claude Desktop, otros LLM y aplicaciones compatibles con MCP.

¿Por qué utilizar Skrape para la integración de LLM?

  • Salida limpia y estructurada : genera Markdown bien formateado que es ideal para el consumo de LLM

  • Reducción de ruido : elimina automáticamente anuncios, menús de navegación y otro contenido irrelevante.

  • Formato consistente : garantiza que el contenido web esté estructurado de manera uniforme independientemente de la fuente.

  • Compatibilidad con JavaScript : gestiona contenido dinámico mediante la representación de JavaScript antes de la conversión

  • Optimizado para LLM : perfecto para alimentar contenido web en LLM como Claude, GPT y otros modelos LLM

Related MCP server: Scraper MCP

Características

Herramientas

  • get_markdown - Convierte cualquier página web a Markdown compatible con LLM

    • Toma cualquier URL de entrada y parámetros opcionales

    • Devuelve un Markdown limpio y estructurado, optimizado para el consumo de LLM

    • Admite la representación de JavaScript para contenido dinámico

    • Formato de respuesta JSON opcional para integraciones avanzadas

Instalación

Instalación mediante herrería

Para instalar Skrape MCP Server para Claude Desktop automáticamente a través de Smithery :

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

Instalación manual

  1. Obtén tu clave API de skrape.ai

  2. Instalar dependencias:

npm install

  1. Construir el servidor:

npm run build

  1. Agregue la configuración del servidor a Claude Desktop:

En MacOS:

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

En Windows:

notepad %APPDATA%/Claude/claude_desktop_config.json

Agregue esta configuración (reemplace las rutas y la clave API con sus valores):

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

Uso con LLM

A continuación se explica cómo utilizar el servidor con Claude u otros modelos LLM:

  1. Primero, asegúrese de que el servidor esté configurado correctamente en su aplicación LLM

  2. Luego, puedes pedirle a ALLMI que obtenga y procese cualquier página web:

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>

El Markdown resultante será limpio, estructurado y listo para el procesamiento LLM.

Opciones avanzadas

La herramienta get_markdown acepta estos parámetros:

  • url (obligatorio): cualquier URL de página web para convertir

  • returnJson (opcional): Establézcalo como true para obtener la respuesta JSON completa en lugar de solo Markdown

  • options (opcional): Opciones de raspado adicionales

    • renderJs : Si se debe renderizar JavaScript antes de raspar (valor predeterminado: verdadero)

Ejemplo con todas las opciones:

<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>

Desarrollo

Para desarrollo con reconstrucción automática:

npm run watch

Depuración

Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP :

npm run inspector

El Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.

Available Tools

1 tool
get_markdownC

Get markdown content from a webpage using skrape.ai

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the webpage to scrape
returnJsonNoWhether to return JSON response (true) or raw markdown (false)
optionsNoAdditional scraping options

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool uses skrape.ai but doesn't describe rate limits, authentication needs, error handling, or what happens if scraping fails. For a web scraping tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the core functionality without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of web scraping (potential for errors, rate limits, etc.), no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like what the return format looks like, error conditions, or usage constraints, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaning beyond what the input schema provides, such as explaining trade-offs between JSON vs. raw markdown or when to adjust JavaScript rendering. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get markdown content from a webpage using skrape.ai'. It specifies the action (get), resource (markdown content), and method (using skrape.ai). However, it doesn't differentiate from siblings since there are none, so it can't earn a 5 for that criterion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It merely states what the tool does without context about appropriate scenarios or constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedget_markdown
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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 issues

Resources

Related MCP Connectors

Related MCP Servers

  • Fetch MCP Server by modelcontextprotocol

    Fetch MCP Serverofficial

    modelcontextprotocol
    A
    license
    A
    quality
    A
    maintenance
    This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
    2
    1
    117,055 PyPI
    90,569
    MIT

  • Scraper MCP

    cotdp
    A
    license
    Not graded
    quality
    D
    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.
    7
    MIT

  • markd-mcp

    mayankfulwariya
    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.
    7 npm
    ISC

  • skrape

    AmokOrg
    A
    license
    Not graded
    quality
    D
    maintenance
    Converts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.
    MIT

Appeared in Searches