ScrapeOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| maps_webA | Browse and scrape any webpage with advanced proxy and rendering capabilities. Best for:
Key Features:
Usage Examples:
Returns: HTML content, or JSON with screenshot (base64) if screenshot=true. IMPORTANT - Default Behavior:
If a request fails:
|
| extract_dataA | Extract structured data from webpages using auto-parsing or LLM-powered extraction. Best for:
Extraction Modes:
Data Schemas (for LLM mode):
Usage Examples:
Returns: Structured JSON or Markdown data extracted from the page. |
| return_linksA | Extract and categorize all URLs from a webpage. Best for:
What it extracts:
URL Processing:
Returns: JSON with two arrays:
Usage Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: maps_web for general browsing and scraping, extract_data for structured data extraction, and return_links for URL extraction. There is no functional overlap.
All tools follow a verb_noun pattern with underscores (maps_web, extract_data, return_links). However, 'maps_web' is a slightly ambiguous verb choice, deviating from the more descriptive verbs like 'extract' and 'return'.
Three tools is low but sufficient for a focused scraping toolkit. They cover the core tasks: browsing, data extraction, and link analysis. Additional tools (e.g., dedicated screenshot) could be added, but the current count is reasonable.
The tool surface covers the primary scraping workflows: browsing with advanced features (maps_web), structured extraction (extract_data), and link discovery (return_links). Minor gaps exist, such as lack of form interaction or session management, but core needs are met.