jlucasmcrell/apify-scrapers

Apify Public Data MCP: 40 Production Data Tools & Public Records
One MCP server gives an AI agent **40 production data extractors** - Google Maps business leads, Google News, Google Autocomplete, LinkedIn and Glassdoor jobs, SEC EDGAR, USAspending, Grants.gov, TED tenders, NHTSA recalls, FEC, EPA, ClinicalTrials.gov, openFDA, Europe PMC, GLEIF, CMS providers, Census geocoding, state business registries, contractor licences, Airbnb, YouTube, Twitch and Google Play - each running as an Actor on your own **Apify** account. Install with uvx apify-data-scrapers (Claude Desktop, Cursor, any MCP client), or call the same Actors directly from Python, Node.js or no-code tools.
Each actor is built with strict schema validation, deterministic field mapping, self-healing DOM selectors, and pay-per-event pricing (per-result rates from **$0.00015**, Actor-start from **$0.0005**; the live Apify Store price is authoritative).
---
Runtime contract and spending control
Since version 1.1.0, calls return {results, status, run?} in both MCP structured content and text. Status is success, partial, empty_unverified, or error; errors include a stable code and retry guidance. Zero rows are not proof that no matching records exist. Existing integrations that parsed a bare result array must now read results. Native dataset field names are preserved.
Each call requests a 120-second Actor timeout and a pay-per-event charge cap of $1 by default. Set APIFY_MAX_CHARGE_USD to adjust the cap. This is per run, not a total account spending limit; platform fees outside Actor event charges may still apply. Up to four calls may run concurrently. Cancelling a request attempts to abort its cloud run; check the returned run ID if confirmation fails. An ambiguous start is never retried automatically.
The MCP executable is Python; Node.js files are direct Actor API examples, not a second MCP server. Private queued Actors are omitted from this public catalog.
Quick Navigation
- Make.com templates
- Use-case guides
- Available Extractors & Store Listings
- Python Quickstart
- Node.js Quickstart
- No-Code & Automation Workflows (n8n, Sheets, Slack)
- Pre-Built Example Tasks (Zero Code)
- Free Sample Datasets
- AI Agent & MCP Integration (Claude Desktop, Cursor, Custom Agent)
- In-Depth Engineering Guides
- Repository Structure
- Contributing & Author
---
Choose your tools
Choose a focused tool profile and generate your installation configuration.
Version 1.2.0 adds the optional APIFY_TOOL_PROFILE environment variable: all (default), leads, market, government, or research. These correspond to the four catalog categories below. Profiles restrict tool discovery and calls, prompts, and the Actor catalog. Restart the MCP server and refresh/reconnect your client after changing the profile. Keep only the focused server entry if you do not also want the full catalog loaded. Direct Actor API examples are unchanged; this setting is not an Apify account permission boundary.
Choose your first workflow
| Your goal | Start here | What to expect |
|---|---|---|
| Build a local contractor lead list | Dallas electrician example task | Review the prefilled input, set a small result limit, then run and export the dataset. |
| Track company filings | SEC filing-monitor tutorial | Choose companies and form types; retain filing identifiers to avoid duplicate alerts. |
| Compare healthcare providers over time | CMS provider-monitor tutorial | Save snapshots and compare changes in the source dataset, not real-time clinical outcomes. |
| Use an AI chat interface | ChatGPT and Apify MCP setup | Connect your own Apify account and choose the Actor explicitly. |
No separate subscription to this MCP package is required. Actor runs are billed through your Apify account at the displayed Store price. Start with a small run and inspect its output before scheduling recurring work; public-source data can be delayed, incomplete, or temporarily unavailable.
---
Privacy Policy
The MCP server collects nothing. It runs on your machine, reads APIFY_TOKEN from your environment, and its only outbound calls are to the Apify API to run the Actor you asked for — on your own Apify account. No telemetry, no logs, no data sent to us. Full policy: apify.revenuesystemslabs.com/privacy.