# Grepsr MCP for AI Agents AI Agent Connect

> Grepsr MCP lets you manage your web scraping reports and data pipelines directly through your AI client. You can trigger manual crawls, check the status of your data feeds, and pull the latest scraped records into your workspace. It connects your Grepsr account to your agent so you can handle data extraction without leaving your current workflow.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_rm4IJmzbIXXRR9xuzKrFDQdNN050RzzW46QRudzp/ai-agent-connect
- **Tags:** data-extraction, web-crawling, structured-data, data-pipeline, automated-scraping, data-feeds

## Description

This Connector connects your Grepsr account to your AI agent so you can handle web scraping operations through natural language. Instead of jumping between different tabs to check if a crawler finished or to see if a webhook fired, you can just ask your agent to do it for you. You can pull the latest structured data from any report or check the status of your active integrations like S3 or SFTP. It's a way to keep your data pipelines moving without the manual overhead of dashboard navigation. Since Vinkius makes it easy to connect these types of tools to your workflow, you can spend less time clicking and more time using the data you've actually collected. You can audit your reports, trigger on-demand crawls to refresh your datasets, and manage your webhooks all from a single chat interface.

## Tools

### get_me
Fetches the details for your current Grepsr account. Use this to verify your connection is active.

### get_latest_data
Pulls the most recent scraped dataset for a chosen report. This is great for getting a quick preview of new data.

### get_report_data
Queries specific scraped records from a report. Use this to pull actual data points into your chat.

### get_report_details
Pulls the metadata and configuration for a specific scraping report. Use this to see how a crawler is set up.

### get_report_history
Retrieves the execution history and run logs for a report. It helps you audit past crawl successes and failures.

### get_usage_stats
Checks your account API usage and current request limits. Use this to monitor your account health.

### list_integrations
Lists all active data delivery connections like S3 and SFTP. This shows where your data is being sent.

### list_projects
Shows all scraping projects currently in your account. Use this to get a high level view of your work.

### list_reports
Lists every report and crawler available in your Grepsr account. This is the best way to see all active crawlers.

### list_webhooks
Shows the webhooks configured for a specific report. Use this to see where your data notifications are going.

### run_report
Triggers an on-demand crawl for a specific report to refresh data. Use this to get fresh results right now.

### create_webhook
Configures a new webhook URL for a specific report. This lets you send data to your own internal systems.

## 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)
* **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:

| Address | Price |
| :--- | :--- |
| 123 Main St | $450,000 |
| 456 Oak Ave | $320,000 |
| 789 Pine Rd | $580,000 |
| 101 Lake Dr | $950,000 |
| 202 Hill Ct | $275,000 |
```

## Capabilities

### Trigger manual crawls
Start an on-demand crawl for any report to refresh your data immediately.

### Pull latest records
Get the most recent scraped dataset from a specific report into your chat.

### Check crawl history
View the execution logs and record counts for your reports to audit data quality.

### Manage webhooks
Set up and audit webhooks to notify your internal systems as soon as data is ready.

### View delivery integrations
List your active connections to S3, SFTP, and other cloud storage providers.

## Use Cases

### Manual data refresh for pricing
A researcher needs current pricing data. They ask the agent to use run_report to get the latest list from a competitor.

### Audit crawl success
An engineer wants to see if a crawl failed. They ask the agent to check get_report_history for the last 5 runs.

### Automate data alerts
An ops person needs data in a new Slack channel. They ask the agent to create_webhook for a specific report.

### Quick data preview
A user wants to see the last 10 items from a crawler. They ask the agent to use get_latest_data to show the records.

## Benefits

- Trigger refreshes instantly using run_report to get fresh data without waiting for your next scheduled crawl.
- Audit your data quality by checking record counts in get_report_history to ensure no data was missed.
- Automate your notifications by setting up alerts with create_webhook to keep your team informed.
- Simplify your stack by viewing all cloud storage connections via list_integrations in one place.
- Pull specific data points directly into your chat using get_report_data to skip the manual CSV exports.
- Monitor your account health and stay within limits by checking get_usage_stats regularly.

## How It Works

The bottom line is you get a direct line to your web scraping pipeline without the manual dashboard clicking.

1. Subscribe to the Grepsr MCP on Vinkius and copy your API key from your Grepsr profile under Personal Details.
2. Paste the key into your AI client's configuration to link your account.
3. Ask your agent to list reports or trigger crawls to start managing your data pipeline.

## Frequently Asked Questions

**Can I use the Grepsr MCP to start web scraping crawls?**
Yes. You can ask your AI agent to trigger an on-demand crawl for any of your existing reports to refresh your data immediately.

**How does the Grepsr MCP help with data quality?**
It allows you to quickly check the execution history and record counts for your reports, making it easy to audit whether your crawls are successful.

**Can I pull scraped data directly into my AI chat?**
Yes. You can retrieve the most recent dataset or query specific records from a report to see them directly in your conversation.

**Does the Grepsr MCP support cloud storage integrations?**
It allows you to view all your active data delivery integrations, including connections to S3 and SFTP, directly through your agent.

**Can I set up webhooks using the Grepsr MCP?**
Yes. You can configure new webhook URLs for your reports so your internal systems get notified automatically when new data is ready.

**How do I check my Grepsr API usage?**
You can ask your agent to check your account usage stats and request limits to ensure you stay within your plan's boundaries.

**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.