Analytics

Apify MCP Server

Connect your account, then chat with AI to run tools.

Apify is a web scraping and automation platform for extracting data from websites at scale. Search the Apify Store for pre-built scrapers (Actors), run them with custom input, monitor runs, and retrieve structured results from datasets.

48 tools
Agent guide included
Start Chatting

Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.

Browse all tools

AI Skill
SKILL.md

Domain knowledge for Apify — workflow patterns, data models, and gotchas for your AI agent.

Apify

Web scraping and automation platform. Discover scrapers in the Store, run them with custom input, monitor execution, and retrieve structured results.

Entity Hierarchy

  • Actors (scrapers/automations) are the core unit. Each Actor has a unique id (e.g. apify/web-scraper) and versioned Builds.
  • Runs are execution instances of an Actor. A run has a status (READY, RUNNING, SUCCEEDED, FAILED, TIMED-OUT, ABORTED) and a defaultDatasetId.
  • Datasets hold tabular output from runs. Each dataset has paginated Items (the actual scraped data rows).
  • Key-Value Stores hold arbitrary key→value pairs (JSON, HTML, screenshots). Each run gets a default store. The INPUT key holds the run's input config.
  • Request Queues manage URL frontier for crawling Actors. Items are URLs with metadata.
  • Schedules trigger Actor runs on a cron schedule.
  • Webhooks notify external systems on run state changes.

Capability areas

Store & discovery

Keyword search across the public Actor marketplace yields ids, pricing hints, and popularity—use that before committing to a scraper.

Your Actors vs Store Actors

Owned Actors live in a separate inventory from marketplace listings; open a catalog entry to read README, input schema, and recent run stats.

Execution lifecycle

Runs are started with structured JSON input and return immediately while work continues in the background. Historically completed runs, live status, cancel, resurrect, and advanced “morph” controls all hang off the run object.

Outputs

Tabular datasets expose paginated rows; key-value stores hold blobs like screenshots or HTML snapshots; request queues show crawler frontiers. Each finished run points at its default dataset and default store ids.

Account

Profile reads expose quota consumption and plan ceilings.

Workflows

  1. Find and run a scraper: Marketplace search → inspect Actor metadata and input schema → launch with validated JSON → poll run state until success → pull dataset pages for the result grid.
  2. Monitor active runs: Filter the global run list, open a single run for diagnostics, cancel if it is wedged.
  3. Access run artifacts: Read the run payload for defaultDatasetId vs defaultKeyValueStoreId, then fetch tabular rows or individual store records (e.g. rendered PNGs).

Gotchas

  • Async execution: Starts return immediately—poll run state until terminal status. Duration ranges from seconds to hours.
  • Actor ID format: Marketplace Actors use vendor/slug style ids; first-party builds often use opaque hashes.
  • Dataset pagination: Default page sizes are modest—walk with offset/limit when exports spill past the first window.
  • Token scope: API tokens are full-account; assume least-privilege operationally even though the vendor does not offer sub-roles.
  • Run memory: Memory/time drive compute units—compare remaining allowance on the account snapshot when planning big scrapes.

Tools in this Server (48)

Apify Abort Run

Abort a running Apify Actor run. Use gracefully=true to let the Actor save partial results before stopping. Returns the updated run object.

Apify Add Queue Req

Add a single URL request to an Apify request queue. The request will be picked up by an Actor crawling from this queue. Use unique_key for deduplicati...

Apify Batch Queue Reqs

Add multiple URL requests to an Apify request queue in a single batch call. Up to 10,000 requests per call. Returns counts of processed vs unprocessed...

Apify Create Req Queue

Create an Apify request queue. Request queues manage URL crawl queues for Actors. Use apify_add_queue_req to add URLs to the queue.

Apify Create Schedule

Create an Apify schedule to automatically run Actors or tasks on a cron schedule. Define the cron expression, timezone, and which Actors/tasks to run.

Apify Create Task

Create a saved Apify Actor task with pre-configured input and options. Tasks let you save common Actor configurations for reuse.

Apify Create Webhook

Create an Apify webhook. Webhooks send HTTP POST requests to your URL when Actor run events occur (succeeded, failed, timed out, etc). Use conditions ...

Apify Delete Schedule

Delete an Apify schedule. This permanently removes the schedule and stops all future runs.

Apify Delete Task

Delete a saved Apify Actor task. This permanently removes the task configuration.

Apify Delete Webhook

Delete an Apify webhook. This permanently removes the webhook.

Apify Del Queue Req

Delete a specific request from an Apify request queue.

Apify Get Actor

Get detailed information about a specific Apify Actor including its name, description, default run configuration (memory, timeout), input schema, stat...

Apify Get Dataset

Get metadata about a specific Apify dataset including item count, size, creation date, and modification date. Use apify_get_dataset_items to fetch the...

Apify Get Dataset Items

Get items (scraped data) from an Apify dataset. This is how you retrieve results after running an Actor. Pass the defaultDatasetId from the run respon...

Apify Get Dataset Stats

Get statistics for an Apify dataset including item count, data size, field frequencies, and data quality metrics.

Apify Get Dispatch

Get details of a specific Apify webhook dispatch including the request sent, HTTP response received, status, and timing.

Apify Get Kv Record

Get a specific record from an Apify key-value store. Returns the record's content (JSON, text, or binary reference). Use apify_get_kv_store_keys to di...

Apify Get Kv Store Keys

List keys in an Apify key-value store. Returns key names, sizes, and content types. Common keys include 'INPUT' (run input), 'OUTPUT' (run output), an...

Apify Get Queue Head

Get the next pending requests from the head of an Apify request queue. Returns the URLs that would be processed next by a crawling Actor.

Apify Get Queue Req

Get details of a specific request in an Apify request queue including URL, method, handled status, retry count, and error messages.

Apify Get Req Queue

Get details of an Apify request queue including total, handled, and pending request counts, creation date, and modification date.

Apify Get Run

Get status and details of an Apify Actor run. Returns status (READY, RUNNING, SUCCEEDED, FAILED, ABORTED, TIMED-OUT), timing info, defaultDatasetId (f...

Apify Get Run Log

Get the console log output of an Apify Actor run. Useful for debugging failed runs or monitoring progress. Returns the log as plain text.

Apify Get Schedule

Get details of an Apify schedule including its cron expression, timezone, associated Actors/tasks, enabled status, and next run time.

Apify Get Schedule Log

Get the execution log for an Apify schedule showing when it ran, what actions were triggered, and any errors.

Apify Get Task

Get details of a saved Apify Actor task including its name, associated Actor, saved input configuration, memory/timeout settings, and run history.

Apify Get Usage

Get the current month's usage statistics for your Apify account. Returns compute units used, data transfer, storage usage, and costs against your plan...

Apify Get User

Get the current Apify user's account info including username, email, plan details, usage limits, and proxy settings. Use this to check account status ...

Apify Get Webhook

Get details of an Apify webhook including its URL, event types, condition, request template, headers, and associated Actor/task.

Apify List Actors

List Actors in your Apify account. Returns Actor IDs, names, descriptions, creation dates, and run stats. Use 'my=true' to filter to only your own Act...

Apify List Datasets

List datasets in your Apify account. Each Actor run creates a default dataset with scraped results. Returns dataset IDs, names, item counts, and creat...

Apify List Dispatches

List webhook dispatches across your Apify account. Shows delivery history for all webhooks including dispatch IDs, statuses, HTTP response codes, and ...

Apify List Kv Stores

List key-value stores in your Apify account. Each Actor run creates a default key-value store for storing intermediate data, screenshots, and other ou...

Apify List Queue Reqs

List requests in an Apify request queue. Returns URLs, methods, unique keys, and handled status for each request in the queue.

Apify List Req Queues

List request queues in your Apify account. Request queues manage URL crawl queues for Actors. Returns queue IDs, names, pending/handled request counts...

Apify List Runs

List Actor runs across your Apify account. Returns run IDs, statuses, Actor IDs, timing, and dataset IDs. Filter by status to find running, succeeded,...

Apify List Schedules

List schedules in your Apify account. Schedules automatically run Actors or tasks on a cron-based schedule. Returns schedule IDs, names, cron expressi...

Apify List Task Runs

List runs of a specific saved Apify Actor task. Returns run IDs, statuses, timing info, and dataset IDs for each execution of this task.

Apify List Tasks

List saved Actor tasks in your Apify account. Tasks are pre-configured Actor runs with saved input, memory, and timeout settings. Returns task IDs, na...

Apify List Webhooks

List webhooks in your Apify account. Webhooks send HTTP requests when Actor runs succeed, fail, or other events occur. Returns webhook IDs, URLs, even...

Apify Resurrect Run

Resurrect a finished Apify Actor run. This restarts the run from where it left off, preserving the existing dataset, key-value store, and request queu...

Apify Run Actor

Run an Apify Actor (web scraper or automation). Pass the Actor ID and input parameters. The run starts asynchronously — use apify_get_run to poll stat...

Apify Run Task

Run a saved Apify Actor task. Tasks have pre-configured input, memory, and timeout settings. Optionally pass run_input to override specific fields. Re...

Apify Search Store

Search the Apify Store for pre-built Actors (web scrapers and automations). Find scrapers for specific websites or use cases like LinkedIn companies, ...

Apify Test Webhook

Test an Apify webhook by sending a sample event dispatch to the webhook URL. Returns the dispatch result including HTTP status code from your endpoint...

Apify Update Schedule

Update an existing Apify schedule. Change the cron expression, timezone, actions, or enable/disable the schedule. Only include fields you want to chan...

Apify Update Task

Update an existing Apify Actor task. Change the name, input configuration, or run options. Only include fields you want to change.

Apify Update Webhook

Update an existing Apify webhook. Change the URL, event types, conditions, payload template, or description. Only include fields you want to change.

Frequently Asked Questions

What is the Apify MCP server?

Apify is a web scraping and automation platform for extracting data from websites at scale. Search the Apify Store for pre-built scrapers (Actors), run them with custom input, monitor runs, and retrieve structured results from datasets. It provides 48 tools that AI agents can use through the Model Context Protocol (MCP).

How do I connect Apify to my AI agent?

Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/apify. Authentication is handled automatically.

How many tools does Apify provide?

Apify provides 48 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.

What authentication does Apify require?

Apify uses API Key. Apify requires credentials. Connect via MCPBundles and authentication is handled automatically.

Setup Instructions

Connect Apify to any MCP client in minutes

https://mcp.mcpbundles.com/bundle/apify

What is MCP?

Model Context Protocol lets AI tools call external capabilities securely through a single URL. This bundle groups tools behind an MCP endpoint that many clients can use.

Use this bundle in 3 steps

  1. Copy the MCP URL above
  2. Open your AI tool and add a new MCP/connector
  3. Paste the URL and follow any auth prompts

Claude Desktop Users

Skip the manual setup! Use the .mcpb file format for one-click installation. Check the Claude Desktop tab for setup instructions.

Pick your tool tab for exact steps

Select ChatGPT, Cursor, Claude Code, or another tab for copy-paste config.

Ready to use Apify?

Sign in to connect your credentials and start running tools from the chat.

Apify MCP Server & Skill — 48 Tools