Scrapi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Your Scrapi API key, alternative to SCRAPI_API_KEY environment variable. | |
| SCRAPI_API_KEY | No | Your Scrapi API key (hsmcp_...). Can also be passed via --api-key CLI argument. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_urlA | Scrapes a webpage and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering. |
| scrape_urlsA | Scrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering. |
| get_usageA | Check API usage and remaining credits. Returns current plan, subscription credits, purchased credits, and total remaining credits. |
| scraper_server_statusA | Check the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times. |
| get_billingA | Retrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits. |
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 5 tools
Each tool has a distinct purpose: billing info, usage credits, server status, single scrape, and batch scrape. The two billing/usage tools are related but their descriptions clearly differentiate scope, so an agent can distinguish them.
Most tools follow verb_noun pattern (e.g., get_billing, scrape_url), but 'scraper_server_status' uses a noun phrase without a clear verb, introducing inconsistency. The naming is readable but not fully uniform.
With 5 tools, the set is well-scoped for the server's purpose: core scraping functionality (single and batch), server monitoring, and account/usage management. Each tool is necessary and none are redundant.
The tool set covers essential actions like scraping and checking status/billing, but lacks management operations such as stopping a scrape, updating billing plans, or configuring scrape options. This creates notable gaps that agents may need to work around.