Skip to main content
Glama
Scrapezy

Scrapezy

Official
by Scrapezy

@scrapezy/mcp MCP Server

A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.

Features

Tools

  • extract_structured_data - Extract structured data from a website

    • Takes URL and prompt as required parameters

    • Returns structured data extracted from the website based on the prompt

    • The prompt should clearly describe what data to extract from the website

Related MCP server: spider-cloud-mcp

Installation

Installing via Smithery

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

npx -y @smithery/cli install @Scrapezy/mcp --client claude

Manual Installation

npm install -g @scrapezy/mcp

Usage

API Key Setup

There are two ways to provide your Scrapezy API key:

  1. Environment Variable:

    export SCRAPEZY_API_KEY=your_api_key
    npx @scrapezy/mcp
  2. Command-line Argument:

    npx @scrapezy/mcp --api-key=your_api_key

To use with Claude Desktop, add the server config:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "scrapezy": {
      "command": "npx @scrapezy/mcp --api-key=your_api_key"
    }
  }
}

Example Usage in Claude

You can use this tool in Claude with prompts like:

Please extract product information from this page: https://example.com/product
Extract the product name, price, description, and available colors.

Claude will use the MCP server to extract the requested structured data from the website.

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

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

License

MIT

Available Tools

1 tool
extract-structured-dataC

Extract structured data from a website.

Inputs: prompt (required), url (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as extracting structured data from websites, leaving no room for confusion.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern ('extract-structured-data'), and since there are no other tools, consistency is inherently perfect with no deviations or mixed conventions.

    Tool Count2/5

    One tool is too few for a server named 'Scrapezy', which suggests a scraping or data extraction domain. A single tool limits functionality and feels thin, as typical scraping tasks might require multiple operations like listing URLs or handling different data formats.

    Completeness2/5

    The tool surface is severely incomplete for a scraping domain. It only provides extraction, with obvious gaps such as no tools for discovering URLs, navigating pages, handling authentication, or managing scraping sessions, which will likely cause agent failures in real-world scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers