The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Scrapi listing page.
⚡ Fast & Reliable — Built on 8+ years of web scraping expertise, 1,900+ production crawlers, and battle-tested anti-bot handling.
What is this?
An MCP (Model Context Protocol) server that lets AI agents fetch and read web pages. Simply give it a URL, and it returns clean, LLM-ready content — fast.
Before: AI can't read web pages directly After: "Summarize this article" just works ✨
# Clone the repository
git clone https://github.com/bamchi/scrapi-mcp-server.git
cd scrapi-mcp-server
# Install dependencies and build
npm install && npm run build
Note: Claude Desktop requires the mcp-remote proxy for HTTP connections.
Self-host the HTTP server (advanced)
Run your own instance instead of using the hosted endpoint:
bash
SCRAPI_API_KEY=your-api-key npx -y -p @scrapi.ai/mcp-server scrapi-http
# or from source:
SCRAPI_API_KEY=your-api-key node dist/http.js
The server starts at http://localhost:3000 with the MCP endpoint at /mcp. Configure with PORT and HOST environment variables. Replace the URL in the client configurations above with your self-hosted URL (e.g. http://localhost:3000/mcp).
Health check:GET http://localhost:3000/health
Step 3: Restart Your AI Client
Claude Desktop: Fully quit (Cmd+Q on macOS, Alt+F4 on Windows) and reopen
Claude Code: Restart the session
Cline: Restart VS Code
Cursor: Restart the editor
You should see the MCP server connection indicator.
Available Tools
scrape_url
Scrapes a webpage and returns AI-readable content.
# Article Title
> Author: John Doe | Published: 2024-01-15## Introduction
This is the main content of the article, converted to clean markdown...
## Key Points
- Point 1: Important detail
- Point 2: Another insight
- [Related Link](https://example.com/related)
Text Output:
text
Article Title
Author: John Doe | Published: 2024-01-15
Introduction
This is the main content of the article, converted to plain text...
Key Points
- Point 1: Important detail
- Point 2: Another insight
scrape_urls
Scrapes multiple webpages in parallel and returns AI-readable content.
[
{
"url": "https://example.com/page1",
"content": "Page 1 Title\n\nThis is the content of page 1..."
},
{
"url": "https://example.com/page2",
"content": "Page 2 Title\n\nThis is the content of page 2..."
}
]
scraper_server_status
Check the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and timing info.
Parameters: None
Example:
config.json
{}
Output:
markdown
## ScraperServer Status
Total: 3 | Available: 2
| Name | OS | Status | Failures | Last Success | Last Failure |
|------|----|--------|----------|--------------|--------------|
| pluto | linux | OK | 0 | 01/3014:23:05 | - |
| mars | mac | FAIL | 2 | 01/2910:00:00 | 01/3013:55:12 |
| venus | linux | OPEN | 3 | 01/2809:00:00 | 01/3012:00:00 |
### Issues
- **mars**: Connection refused - connect(2)
- **venus**: Circuit breaker open until 01/3012:30:00
- **venus**: Net::ReadTimeout
Status values:
Status
Description
OK
Server is healthy
FAIL
Server is unhealthy
OPEN
Circuit breaker open (isolated for 30 min)
N/A
Not yet checked
get_usage
Check your API usage and remaining credits.
Parameters: None
Example:
config.json
{}
Output:
markdown
## MCP Credits
| Item | Value |
|------|-------|
| Plan | starter |
| Subscription Credits | 1,500 |
| Purchased Credits | 200 |
| Total Remaining | 1,700 |
| Period End | 2026-03-01 |
get_billing
Retrieve detailed billing information including subscription, plans, daily usage, and spending limits.
Parameters:
Name
Type
Required
Description
action
string
Yes
subscription, plans, daily_usage, or spending_limits
start_date
string
Start date for daily_usage (YYYY-MM-DD, default: 30 days ago)
end_date
string
End date for daily_usage (YYYY-MM-DD, default: today)
Example — Current subscription:
config.json
{ "action": "subscription" }
markdown
## MCP Subscription
| Item | Value |
|------|-------|
| Plan | starter (Starter) |
| Status | active |
| Monthly Credits | 2,000 |
| Price | $19.00/mo |
| Rate Limit | 30 RPM |
| Burst Limit | 5 concurrent |
| Period End | 2026-03-01 |
User: Summarize this article: https://news.example.com/article/12345
Claude: [calls scrape_url]
Here's a summary of the article:
## Key Points
- Point 1: ...
- Point 2: ...
- Point 3: ...
Example 2: Fetch Page Content
Code
User: Get the content from https://example.com/data
Claude: [calls scrape_url]
# Page Title
> Source: https://example.com/data
The page content is returned in clean Markdown format...
Example 3: Research Competitor Pricing
Code
User: What's the pricing on https://competitor.com/product/abc
Claude: [calls scrape_url]
Here's the pricing information:
- **Product**: ABC Premium
- **Regular Price**: $99.00
- **Sale Price**: $79.00 (20% off)
Example 4: Read API Documentation
server.ts
User: Read https://docs.example.com/api/v2 and write integration code
Claude: [calls scrape_url]
I've analyzed the API documentation. Here's the integration code:
// api-client.ts
exportclass ExampleApiClient {
private baseUrl = 'https://api.example.com/v2';
async getData(): Promise<Response> {
// ...
}
}
How It Works
Code
┌─────────────────┐
│ User │
│ "Summarize this │
│ URL for me" │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Claude Desktop │
│ / Cursor │
└────────┬────────┘
│
▼
┌─────────────────┐ ┌─────────────────┐
│ MCP Server │────►│ Scrapi API │
│ (scrape_url) │ │ (format param) │
└────────┬────────┘ └────────┬────────┘
│ │
│◄──────────────────────┘
│ Markdown/Text Response
▼
┌─────────────────┐
│ AI Response │
│ (Summary, etc.) │
└─────────────────┘
Why Scrapi?
Built by the team behind Scrapi, with 8+ years of web scraping experience:
✅ 1,900+ production crawlers
✅ JavaScript rendering support
✅ Anti-bot handling
✅ 99.9% uptime
Troubleshooting
"API key is required"
Make sure your API key is provided via one of these methods:
Environment variable: Set SCRAPI_API_KEY in your configuration
CLI argument: Pass --api-key your-key in the args
"Invalid API key"
Verify that your API key is correct and active in your Scrapi dashboard.
npx using an old cached version
If you upgraded but still see old behavior, clear the npx cache:
Terminal
npx clear-npx-cache
MCP Server not connecting
Ensure Node.js 20+ is installed
Try running node /absolute/path/to/scrapi-mcp-server/dist/index.js manually to check for errors
Fully quit Claude Desktop (Cmd+Q on macOS, Alt+F4 on Windows) and restart
Check Settings > Developer to verify the server is listed
Developer tab not visible
Update Claude Desktop to the latest version: Claude menu → "Check for Updates..."