Skip to main content
Glama
enesjakozh
tanevanwifferen

UseScraper MCP Server

by tanevanwifferen
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

UseScraper MCP Server

This is a TypeScript-based MCP server that provides web scraping capabilities using the UseScraper API. It exposes a single tool 'scrape' that can extract content from web pages in various formats.

Features

Tools

  • scrape - Extract content from a webpage

    • Parameters:

      • url (required): The URL of the webpage to scrape

      • format (optional): The format to save the content (text, html, markdown). Default: markdown

      • advanced_proxy (optional): Use advanced proxy to circumvent bot detection. Default: false

      • extract_object (optional): Object specifying data to extract

Related MCP server: MCP-Typescribe

Installation

Installing via Smithery

To install UseScraper for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install usescraper-server --client claude

Manual Installation

  1. Clone the repository:

    git clone https://github.com/your-repo/usescraper-server.git
cd usescraper-server

  2. Install dependencies:

    npm install

  3. Build the server:

    npm run build

Configuration

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": {
    "usescraper-server": {
      "command": "node",
      "args": ["/path/to/usescraper-server/build/index.js"],
      "env": {
        "USESCRAPER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Replace /path/to/usescraper-server with the actual path to the server and your-api-key-here with your UseScraper API key.

Usage

Once configured, you can use the 'scrape' tool through the MCP interface. Example usage:

{
  "name": "scrape",
  "arguments": {
    "url": "https://example.com",
    "format": "markdown"
  }
}

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, which is available as a package script:

npm run inspector

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

Available Tools

1 tool
scrapeC

Scrape content from a webpage using UseScraper API

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scrape
formatNoFormat to save crawled page content. Strongly recommended to keep as markdown for optimal AI processing (default: markdown)
advanced_proxyNoUse advanced proxy to circumvent bot detection (default: false)
extract_objectNoOptional object specifying data to extract

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits beyond the API name. It does not mention rate limits, authentication, potential failures, or what happens with the proxy option. The schema provides some param hints, but the description adds no behavioral context.

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

Conciseness4/5

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

The description is a single sentence, concise and front-loaded. It is appropriately sized for a simple tool, though it could include a bit more detail without becoming verbose.

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 tool has 4 parameters, nested objects, and no output schema, the description is too minimal. It does not explain what is returned or how the tool behaves in edge cases, leaving significant gaps for an 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 coverage is 100% with each parameter described, so the baseline is 3. The description adds minimal extra meaning beyond stating the API, so it meets the baseline without enhancing understanding.

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 identifies the action (scrape) and resource (webpage), naming the API used (UseScraper). However, 'scrape' is broad and could be more specific about what types of content or how it extracts, but without siblings it's sufficiently clear.

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?

No guidance is provided on when to use this tool versus alternatives or any exclusions. The description only states what it does, leaving the agent to infer usage context.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools.

Naming Consistency5/5

With a single tool, naming is trivially consistent.

Tool Count3/5

A single tool for web scraping is borderline; it might suffice for basic use but feels thin for a full-featured scraper server.

Completeness3/5

The single scrape tool covers the core functionality, but lacks additional features like selecting specific elements or handling different output formats, which are common in web scraping APIs.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Scrapezy by Scrapezy

    Scrapezyofficial

    Scrapezy
    A
    license
    C
    quality
    C
    maintenance
    MCP Server enabling integration with Scrapezy to retrieve structured data from websites.
    1
    25
    13
    MIT

  • MCP-Typescribe

    yWorks
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables LLMs to understand and work with TypeScript APIs they haven't been trained on by providing structured access to TypeScript type definitions and documentation.
    30
    46
    MIT

  • Web Scraper MCP Server

    naku111
    A
    license
    A
    quality
    D
    maintenance
    A TypeScript-based web scraping server built on the Model Context Protocol that offers multiple export formats, content extraction rules, and support for both static and dynamic (SPA) websites.
    7
    12
    1
    MIT

  • Angular Bootstrap MCP Server

    palsuman
    A
    license
    Not graded
    quality
    D
    maintenance
    A TypeScript-based MCP server that provides backend API handling and facilitates communication between microservices. Features an organized structure with controllers, routes, and models for easy extensibility and maintenance.
    225
    1
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tanevanwifferen/usescraper-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server