# Grepsr MCP MCP

> Grepsr lets you take full control of your web scraping data directly through your AI client. Instead of logging into a dashboard to check on crawls or download reports, you tell your agent exactly what data you need—whether it's the latest product price list or an entire competitor report history—and get structured records right in your workflow.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** data-extraction, web-crawling, structured-data, data-pipeline, automated-scraping, data-feeds

## Description

Imagine needing to track every time a competitor changes its pricing structure. Instead of building custom scripts and managing API keys across multiple services, you connect this MCP and give your AI agent permission to manage all your web scraping jobs. You can tell it to trigger an immediate crawl for a specific site or ask for the 50 most recent records from last week's run. Your agent handles everything: running the job, tracking its status, retrieving the structured data when it’s ready, and even setting up automated alerts so you know instantly when new information drops into your systems. This gives you total visibility over all your managed scraping operations, letting your AI client act as the central control panel for all your web data feeds.

## Tools

### create_webhook
Sets up a new webhook URL to notify your systems when a specific report is updated.

### get_me
Gets basic details about your current Grepsr account configuration.

### get_latest_data
Retrieves the most recent scraped dataset for a given report ID.

### get_report_data
Queries and fetches structured records from a specific, named report.

### get_report_details
Retrieves the metadata and setup configuration for any specified report.

### get_report_history
Pulls a log of all previous execution runs (histories) for a given report.

### get_usage_stats
Checks your account's API usage and current request rate limits.

### list_integrations
Lists all active data delivery connections, like S3 or SFTP.

### list_projects
Shows a list of every scraping project you have created.

### list_reports
Lists all web scraping reports and crawlers within your account.

### list_webhooks
Shows a list of the webhook URLs currently set up for a specific report.

### run_report
Manually starts an on-demand crawl run to refresh data for any specified report.

## Prompt Examples

**Prompt:** 
```
List my web scraping reports in Grepsr
```

**Response:** 
```
Retrieving your reports... I found 3 active crawlers: 'Amazon Product Data' (ID: 104), 'LinkedIn Jobs' (ID: 105), and 'Real Estate Listings' (ID: 108). Would you like to see the latest data for any of these?
```

**Prompt:** 
```
Trigger a manual crawl for report ID 104
```

**Response:** 
```
Starting crawl... Success! I've triggered a manual run for 'Amazon Product Data' (ID: 104). The status is now 'In Progress'. I can check back in a few minutes to see when the data is ready.
```

**Prompt:** 
```
Show me the 5 most recent records from the 'Real Estate Listings' report
```

**Response:** 
```
Fetching records... Here are the 5 latest items from your real estate crawler:
1. 123 Main St - $450,000
2. 456 Oak Ave - $320,000
3. 789 Pine Rd - $580,000
4. 101 Lake Dr - $950,000
5. 202 Hill Ct - $275,000
```

## Capabilities

### Get account status
Retrieve current usage statistics and API rate limit information for your Grepsr account.

### List available projects
See an overview of all scraping projects you have set up in the platform.

### Manage reports list
Fetch a complete list of all active reports and crawlers configured for your account.

### Trigger new crawls
Manually start an immediate crawl run for any specific report to refresh your data.

### Fetch structured records
Query and get the actual, clean dataset from a specified report or historical run.

### Check execution history
Review the full log of runs for a particular report to audit data quality and status.

## Use Cases

### Competitor Pricing Monitoring
A market researcher needs daily price data for 50 products. Instead of writing complex scheduled jobs, they tell their agent to 'trigger a crawl' and then ask the agent to fetch structured records using 'get_report_data', ensuring the pricing feed is always current.

### Data Pipeline Auditing
An operations team needs to confirm if the data delivery worked last night. They can use 'list_integrations' and then check the run status with 'get_report_history' before notifying stakeholders, guaranteeing reliable reporting.

### On-Demand Data Retrieval
A developer needs to validate a specific set of data points immediately. They can ask for the latest items using 'get_latest_data', rather than waiting for the scheduled batch job to run.

### System Integration Alerting
A product manager wants their CRM updated instantly when a new report is ready. They use 'create_webhook' to set up a trigger, letting the system handle the notification automatically instead of manual checks.

## Benefits

- You stop manually checking dashboards. By using 'run_report', you trigger a crawl simply by asking your agent, getting fresh data immediately.
- Never lose track of what's running again. You can check the full execution history using 'get_report_history' to audit data quality and status instantly.
- Setting up alerts is simple. Use 'create_webhook' to ensure that when new data arrives, your internal systems get notified automatically.
- You gain total visibility into where your data goes. 'list_integrations' shows you every connected endpoint, including S3 or SFTP.
- Need to know what the reports are? Running 'list_reports' gives you a quick inventory of all your configured crawlers in one prompt.

## How It Works

The bottom line is that you manage complex data pipelines using natural language prompts in any MCP-compatible client.

1. First, connect your AI agent by providing your Grepsr API key through Vinkius.
2. Next, tell your agent what you need—for example, 'Trigger a crawl for the Amazon product report.'
3. Your agent executes the task, monitors the status, and delivers the resulting structured data directly into your conversation.

## Frequently Asked Questions

**How do I see what reports are available with the Grepsr MCP?**
Use 'list_reports'. This tool retrieves a comprehensive list of all your configured crawlers and reports in one go, so you know exactly what data sources exist.

**What if I need to update an existing report? Do I use the Grepsr MCP?**
If the crawl is already set up, you just trigger a refresh by using 'run_report'. This tells your agent to run a new instance of the job without changing its core configuration.

**Can I check if my data delivery system is working?**
Yes. Use 'list_integrations' to see every active connection (like SFTP or S3) and confirm that your external systems are set up correctly for receiving scraped data.

**Is there a tool to get the latest data quickly?**
You can use 'get_latest_data'. This function retrieves the most recent version of a dataset immediately, saving you from having to query deep historical logs.

**How do I check my API quota or rate limits using the `get_usage_stats` tool?**
The `get_usage_stats` tool provides a direct count of your remaining API usage and defined request limits. This tells you exactly how many runs or data queries you have left for the billing period.

**If I need specific records, how do I query them using the `get_report_data` tool?**
You use `get_report_data` by specifying a report ID and the exact fields you want to retrieve. This lets your agent pull only the structured data points you need, rather than massive full datasets.

**What is the process for setting up automated alerts using the `create_webhook` tool?**
The `create_webhook` tool allows you to define a specific URL that Grepsr sends data to immediately after a successful crawl. This bypasses manual checks and notifies your internal systems instantly.

**When a crawl fails, how can I diagnose the issue with the `get_report_history` tool?**
The `get_report_history` tool pulls the full execution log for any report. You can review past runs to see the failure status, error messages, and which steps failed within the scrape process.

**Can my agent trigger a new web crawl in Grepsr?**
Yes. Use the 'run_report' tool. By providing the Report ID, the agent can programmatically trigger an on-demand crawl, starting the data extraction process immediately flawlessly.

**How do I retrieve the actual scraped data records via chat?**
You can use the 'get_report_data' or 'get_latest_data' tools. Your agent will fetch the structured records from Grepsr's database and present them in a readable format within your chat interface flawlessly.

**Can I check my API usage limits through the agent?**
Absolutely. Use the 'get_usage_stats' tool. Your agent will retrieve your current plan limits and remaining API credits, helping you manage your data extraction budget flawlessly.