Apify

Apify MCP Connector for Claude

A+

Command Apify scrapers from your AI agent — run actors, extract web data, poll datasets, and automate browser tasks seamlessly.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Apify workspace to your AI agent and seamlessly direct full-stack web scraping and data extraction workflows through natural conversation.

What you can do

  • Discover & Run Actors — Browse all scraper bots (Actors) available in your account. Fire them off asynchronously or synchronously for fast, targeted scraping
  • Extract Datasets — Pull robust structured data formats out of completed runs. Retrieve detailed JSON records directly into the agent's context window
  • Fetch Key-Value Stores — Programmatically read snapshots, cached HTML pages, or screenshots from the Apify Key-Value repositories mapped to a run
  • Job Control & Scalability — Stop hanging scraper jobs, queue new dynamic URLs mid-run, or inspect deep usage analytics, compute units, and webhooks limits

How it works

  1. Subscribe to this server
  2. Enter your Personal Apify API Token
  3. Start exploring and interacting with data extraction routines securely via Claude or Cursor

Who is this for?

  • Data Engineers — trigger scheduled extraction logic seamlessly and map Apify objects within a conversational QA check
  • Market Researchers — command the AI to scrape product prices using Apify actors and compile the JSON datasets into readable markdown tables
  • AI Developers — augment your agent's real-time capabilities by feeding it massive structured site data freshly scraped via headless browsers
web-automationdata-extractionproxy-servicesheadless-browserdatasetsapi-integration

10 tools expose this connector's capabilities to your AI agent.

abort_run

Any data already scraped and pushed to the dataset is preserved. The run status changes to ABORTED. Use this to stop runaway scrapes or when sufficient data has been collected. Graceful shutdown depends on the actor implementation. Abort an active Apify actor run

get_account_limits

Essential for monitoring consumption and avoiding overage charges. Check Apify account subscription limits and compute unit usage

get_dataset_items

The datasetId is found in the run object (defaultDatasetId). Supports pagination via limit (max items per page) and offset (starting position). Returns an array of JSON objects containing the scraped data fields. Use limit=1000 for bulk downloads. Export structured JSON data from an Apify dataset

get_key_value_store

Key-value stores hold arbitrary data like screenshots (OUTPUT), configuration files, or intermediate results. The storeId comes from the run object (defaultKeyValueStoreId). Common keys include "OUTPUT", "INPUT", and "SCREENSHOT". Retrieve an item from an Apify actor key-value store

get_run

Poll this endpoint to track long-running scrapes. Check the status and metadata of a specific Apify actor run

list_actors

Includes owned actors and those from the Apify Store that have been saved. Each entry contains the actorId, name, description, and default run configuration. Use the actorId to trigger runs. List all accessible actors in the Apify account

list_webhooks

RUN.SUCCEEDED, ACTOR.RUN.FAILED), target URLs, and associated actor IDs. Webhooks enable event-driven architectures by notifying external systems when actor runs complete or fail. List all configured webhooks in the Apify account

push_to_queue

Pass the queueId (from the run object) and a JSON string array of request objects, e.g., [{"url":"https://...","uniqueKey":"..."}]. This enables dynamic crawling where new pages are discovered and added during execution. Dynamically push new URLs to an active Apify request queue

run_actor_sync

run_actor but waits for the actor to finish before returning. The response includes the full run object with defaultDatasetId for immediate data retrieval. Best for short-lived actors (under 5 minutes). For long-running scrapes, use the async ap.run_actor instead. Run an Apify actor and block until completion (synchronous)

run_actor

Pass the actorId (e.g., "apify/web-scraper" or a custom ID) and a JSON string with the input configuration (start URLs, proxy settings, max pages, etc.). Returns immediately with a runId. Use ap.get_run to poll for completion and ap.get_dataset_items to retrieve extracted data. Start an Apify actor asynchronously with custom JSON input

See how to talk to your AI agent using Apify.

List all the Apify actors available on my account.

I've scanned your Apify actor catalog. You possess 3 main actors: 'ecommerce-spider-v1' and two public templates 'google-search-scraper' and 'instagram-scraper'. Shall I print their base configurable inputs?

Verify the status of run 'qKpwH9LgC3r0Xm' and show me its final dataset if finished.

I checked run `qKpwH9LgC3r0Xm`. Its current status is `SUCCEEDED`. The run consumed 0.045 Compute Units. I have successfully downloaded the associated dataset (`ds_8aBxP_...`) which yielded 302 product profiles. I'm injecting the top 5 parsed items below.

How are our compute usage limits tracking this current month on Apify?

I pulled your overall compute records. Right now on the 'Scale' plan, your account used 82 out of 100 Compute Units (CU). You've consumed significant resources on proxy bandwidth (1.8TB/2TB) leading to roughly 80% usage threshold. I recommend holding further massive scraped runs until renewal happens on the 10th.

First, find your specific scraping Actor ID via `list_actors`. Then, prompt your agent to execute `run_actor`, providing the target URLs formatted as a structured JSON input payload. It returns a 'Run ID'. You can poll this run via `get_run`, and once it succeeds, the agent calls `get_dataset_items` to pull all acquired data straight to your window.

Related Connectors