Apify MCP server

Read from the package source without running it. The installed server may list more.

• abort_build

  Aborts a running or starting Actor build, immediately halting execution and returning the build's full details. Builds already in a terminal state (FINISHED, FAILED, ABORTING, TIMED-OUT) are unaffected by this call.

• abort_runwrite action

  Aborts a currently starting or running Actor run, returning full run details. Runs already in a terminal state (FINISHED, FAILED, ABORTING, TIMED-OUT) are unaffected.

• add_queue_request

  Adds a new URL request to a specified request queue for processing. If a request with the same uniqueKey already exists in the queue, returns the ID of the existing request instead of creating a duplicate.

• append_dataset_items

  Appends one or more JSON objects to the end of the specified dataset. The entire request is rejected with a 400 error if any item fails schema validation; payloads must not exceed 5 MB.

• batch_add_requests

  Adds up to 25 requests to a specified request queue in a single batch operation. Returns arrays of successfully processed and unprocessed requests, with unprocessed entries recommended for retry using exponential backoff.

• batch_delete_queue_requestswrite action

  Batch-deletes up to 25 requests from a specified request queue, identified by their ID or uniqueKey. Any requests that fail due to rate limiting or internal errors are returned in the response for retry, with exponential backoff recommended.

• build_actor

  Triggers a new build for a specified Actor version, compiling its source code and dependencies into a runnable image. Returns the resulting build object, which may reflect a terminal or transitional status depending on wait time.

• charge_run_eventwrite action

  Charge for one or more occurrences of a configured pay-per-event (PPE) billing event within a specific Actor run. Must be called from within the Actor run using the same API token that started the run.

• check_key_value_store_record_exists

  Checks whether a record exists in a key-value store under a specific key without retrieving its value. Useful for lightweight existence checks before performing read or write operations.

• create_actorwrite action
• create_actor_env_varwrite action

  Creates a new environment variable for a specific version of an Actor. Requires a name and value, with an optional flag to mark the variable as secret.

• create_actor_versionwrite action

  Creates a new version of an Actor by specifying a version number and source type along with the corresponding source details. The source type determines which additional properties are required (e.g., a Git repository URL for GIT_REPO, a tarball URL for TARBALL).

• create_datasetwrite action

  Creates a new dataset for storing structured data and returns its object. If a name is provided and a dataset with that name already exists, the existing dataset object is returned instead.

• create_key_value_storewrite action

  Creates a new key-value store and returns its store object. If a store with the specified name already exists, the existing store is returned instead of creating a duplicate.

• create_request_queuewrite action

  Creates a new request queue and returns its object, or returns the existing queue object if a queue with the given name already exists. Unnamed queues are subject to the platform's data retention policy.

• create_taskwrite action

  Creates a new actor task with the specified configuration, including the target actor, build version, timeout, and memory settings. Returns the full task object upon successful creation.

• create_webhookwrite action
• delete_actorwrite action

  Permanently deletes the specified Actor and all associated data. This action is irreversible.

• delete_actor_runwrite action

  Permanently deletes a finished actor run. Only completed runs can be deleted, and only by the user or organization that initiated the run.

• delete_actor_versionwrite action

  Permanently deletes a specific version of an Actor's source code. This action is irreversible and removes the version along with its associated configuration.

• delete_actor_version_env_varwrite action

  Permanently deletes a specific environment variable from a given Actor version. This action cannot be undone.

• delete_buildwrite action

  Permanently deletes a specific Actor build by its ID. The current default build for an Actor cannot be deleted; only users with build permissions for the Actor may perform this action.

• delete_datasetwrite action

  Permanently deletes a specific dataset and its associated data. This action is irreversible and removes the dataset from the account.

• delete_key_value_storewrite action

  Permanently deletes a key-value store and all of its contents. This action is irreversible and removes the store along with all stored key-value pairs.

• delete_key_value_store_recordwrite action

  Permanently removes a single record from a key-value store by its key. The store itself and all other records remain unaffected.

• delete_queue_requestwrite action

  Permanently removes a specific request from a request queue by its ID. Use this to discard requests that are no longer needed for processing.

• delete_request_lockwrite action

  Releases a lock on a specific request in a queue, making it available for other clients to process. Only the client that originally locked the request (via the lock head operation) can delete its lock.

• delete_request_queuewrite action

  Permanently deletes a request queue and all its associated data. This action is irreversible and removes the queue identified by its ID or name.

• delete_taskwrite action

  Permanently deletes the specified actor task and all associated configuration. This action is irreversible and removes the task from the account.

• delete_webhookwrite action

  Permanently deletes a webhook by its unique identifier. This action is irreversible and will stop all event notifications associated with the webhook.

• get_actor

  Retrieves full details for a specific Actor, including its configuration, settings, and metadata. Use this to inspect an Actor before running it or to verify its current state.

• get_actor_build

  Retrieves full details about a specific Actor build, including its status, timing, and resource usage. Supports synchronous waiting via an optional timeout parameter to avoid polling when monitoring build completion.

• get_actor_env_var

  Retrieves details of a specific environment variable for a given Actor version. If the variable is marked as secret, its value will be omitted from the response.

• get_actor_runwrite action

  Retrieves all details about a specific Actor run, including its status, timing, and usage statistics. Optionally waits synchronously for the run to finish, eliminating the need for repeated polling.

• get_actor_version

  Retrieves detailed information about a specific version of an Actor, including its configuration and metadata. Useful for inspecting the exact state of a particular Actor version.

• get_build_log

  Retrieves the log output for a specific actor build. Supports real-time log streaming while the build is in progress.

• get_dataset

  Retrieves metadata and storage information for a specific dataset by its ID. Note that item count fields may lag up to 5 seconds behind actual data; use the list dataset items endpoint to retrieve the dataset's contents.

• get_dataset_statistics

  Retrieves field-level statistics for a specified dataset. Returns aggregated metrics such as value counts, null rates, and type distributions for each field in the dataset.

• get_default_actor_build

  Retrieves the default build for a specified Actor, optionally waiting synchronously for the build to reach a terminal state. No authentication token is required, though unauthenticated requests will have certain usage cost fields omitted from the response.

• get_key_value_store

  Retrieves full details about a specific key-value store, including its configuration and metadata. Use this to inspect store properties before reading or writing data.

• get_key_value_store_record

  Retrieves the value stored under a specific key in a key-value store, returning the record with its original content type and encoding. Use the attachment parameter to fetch raw HTML content without Apify's security modifications.

• get_last_actor_runwrite action

  Retrieves the most recent run of a specified Actor, with optional filtering by run status. Also serves as the base path for accessing the last run's default storages (log, key-value store, dataset, and request queue) via sub-endpoints.

• get_last_task_runwrite action

  Retrieves the most recent run of a specified actor task, with optional filtering by run status. Also serves as the base path for accessing the last run's default storages (log, key-value store, dataset, request queue) via sub-endpoints.

• get_queue_request

  Retrieves a specific request from a request queue by its ID. Returns the full request details including URL, metadata, and processing status.

• get_request_queue

  Retrieves metadata and configuration details for a specific request queue. Returns the full queue object including its properties and current state.

• get_request_queue_head

  Retrieves the first N requests from the head of a request queue. Returns a `hadMultipleClients` flag indicating whether the queue has been accessed by more than one client, which helps SDKs determine local cache consistency.

• get_task

  Retrieve full details of a specific actor task, including its configuration, settings, and metadata. Use this to inspect an existing task before running or modifying it.

• get_task_input

  Retrieves the input configuration for a specified actor task. Returns the input object that defines the parameters passed to the actor when the task runs.

• get_webhook

  Retrieves full details of a specific webhook by its unique identifier. Returns all webhook configuration and metadata.

• get_webhook_dispatch

  Retrieves a webhook dispatch record by its unique ID, returning full details about the dispatch event, status, and payload.

• list_actor_builds

  Retrieves a paginated list of builds for a specific Actor, with each record containing basic build information. Results are sorted by start time in ascending order by default, supporting incremental fetching as new builds are created.

• list_actor_runs

  Retrieves a paginated list of all Actor runs for the authenticated user, with each item containing basic run metadata. Supports filtering by status and start time, and sorting in ascending or descending order.

• list_actor_runs_by_actor

  Retrieves a paginated list of runs for a specific Actor, with each item containing basic run metadata. Supports filtering by status and start time, and sorting in ascending or descending order.

• list_actor_version_env_vars

  Retrieves all environment variables configured for a specific version of an Actor. Returns a list of environment variable objects, each containing the variable's key, value, and related metadata.

• list_actor_versions

  Retrieves all versions of a specific Actor, returning a list of Version objects with basic information about each version.

• list_actor_webhooks

  Retrieves a paginated list of webhooks associated with a specific Actor, returning basic information about each webhook. Results are sorted by creation date ascending by default, with a maximum of 1000 records per request.

• list_actors

  Retrieves a paginated list of Actors the user has created or used, with options to filter to owned Actors only and sort by creation date or last run time. Returns up to 1000 records per request.

• list_builds

  Retrieves a paginated list of all builds for the authenticated user, with each entry containing basic build information. Records are sorted by start time and the endpoint returns a maximum of 1000 records per request.

• list_dataset_items
• list_datasets

  Retrieves a paginated list of datasets accessible to the user, including basic metadata for each. Supports sorting, filtering by ownership, and optionally including unnamed datasets.

• list_key_value_store_keys

  Retrieves a paginated list of keys from a specified key-value store, including metadata about each key's associated value such as size. Supports filtering by collection or key prefix.

• list_key_value_stores

  Retrieves a paginated list of key-value stores accessible to the user, including basic metadata for each store. Results are sorted by creation date ascending by default, supporting incremental pagination as new stores are created.

• list_queue_requests

  Retrieves a paginated list of requests from a specified request queue. Use exclusiveStartId and limit to page through large queues efficiently.

• list_request_queues

  Retrieves a paginated list of the user's request queues, returning basic metadata for each. Results are sorted by creation date ascending by default, supporting incremental fetching as new queues are created.

• list_task_runs

  Retrieve a paginated list of runs for a specific actor task, including essential metadata for each run. Results can be filtered by status and sorted ascending or descending by start time.

• list_task_webhooks

  Retrieves a paginated list of webhooks associated with a specific Actor task. Results are sorted by creation date and capped at 1000 records per request.

• list_tasks

  Retrieves a paginated list of all actor tasks created or used by the authenticated user. Results are sorted by creation date and capped at 1000 records per request.

• list_webhook_dispatches

  Retrieves a paginated list of webhook dispatches associated with the authenticated user. Results are sorted by creation date and capped at 1000 records per request.

• list_webhook_dispatches_by_webhook

  Retrieves the list of dispatch records for a specific webhook, showing its delivery history and execution events.

• list_webhooks

  Retrieves a paginated list of webhooks created by the authenticated user. Results are sorted by creation date and capped at 1000 records per request.

• lock_queue_head_requests

  Retrieves and locks a specified number of requests from the head of a request queue, preventing other clients or runs from accessing them for the duration of the lock period. Returns a flag indicating whether the queue has been accessed by multiple clients.

• metamorph_runwrite action

  Transforms an active Actor run into a run of a different Actor with new input, seamlessly handing off work without creating a new run. The original run's default storages are preserved and the new input is stored in the same key-value store.

• prolong_request_lock

  Extends the lock duration on a specific request in a queue, preventing other clients from acquiring it. Only the client that originally locked the request can prolong its lock.

• put_store_recordwrite action

  Stores a value under a specific key in a key-value store, with the content type defined by the Content-Type header. Supports Gzip, Deflate, and Brotli compression via the Content-Encoding header to reduce payload size and improve upload speed.

• reboot_actor_runwrite action

  Reboots a currently running Actor run by restarting its container, returning the updated run details. Only runs with a RUNNING status can be rebooted; any data not persisted to a key-value store, dataset, or request queue will be lost.

• resurrect_actor_runwrite action

  Restarts a finished Actor run (with status FINISHED, FAILED, ABORTED, or TIMED-OUT), resuming execution with the same storages and updating its status back to RUNNING. Optionally override the build, timeout, memory, or error-restart behavior from the original run.

• resurrect_runwrite action

  Restarts a finished Actor run (with status FINISHED, FAILED, ABORTED, or TIMED-OUT) by restarting its container with the same storages, updating its status back to RUNNING. Optionally override the build, timeout, memory, and cost limits used for the resurrected run.

• run_actorwrite action
• run_actor_syncwrite action

  Runs a specific Actor synchronously, passing the request body as INPUT, and returns the Actor's OUTPUT from its default key-value store. If the Actor run exceeds 300 seconds, the response will return a 408 timeout status.

• run_actor_sync_get_dataset_itemswrite action
• run_actor_sync_get_dataset_items_with_inputwrite action
• run_actor_sync_no_inputwrite action

  Runs a specific Actor synchronously without input and returns its output directly in the response. The run must complete within 300 seconds; if it exceeds this limit or the connection breaks, a timeout error is returned.

• run_taskwrite action

  Starts an Actor task run asynchronously and immediately returns a run object without waiting for completion. Optionally override the task's input configuration via the request body, and use the returned run ID to poll for results or fetch dataset output.

• run_task_syncwrite action

  Runs an Actor task synchronously and returns its output directly in the response. The task must complete within 300 seconds; optionally, you can override the task's default input by providing a JSON payload.

• run_task_sync_and_get_dataset_itemswrite action
• run_task_sync_getwrite action

  Runs a specific actor task synchronously and returns its output directly in the response. The task must complete within 300 seconds; if it exceeds this limit or the connection drops, the request fails but the underlying run continues.

• run_task_sync_get_dataset_itemswrite action
• test_webhookwrite action

  Sends a test dispatch to the specified webhook using a dummy payload. Useful for verifying that the webhook endpoint is correctly configured and reachable.

• unlock_queue_requests

  Unlocks all currently locked requests in the specified request queue that are held by the calling client. Within an Actor run, this releases locks held by both the current run and the same clientKey; outside a run, it releases all locks associated with the provided clientKey.

• update_actorwrite action
• update_actor_env_varwrite action

  Updates an existing environment variable for a specific Actor version. Only the properties included in the request body will be modified; omitted properties retain their current values.

• update_actor_versionwrite action

  Updates a specific version of an Actor with the provided fields, leaving unspecified properties unchanged. Send a JSON payload with only the fields you want to modify.

• update_datasetwrite action

  Updates a dataset's name and general access level by dataset ID or username-scoped name. Returns the full updated dataset object.

• update_key_value_storewrite action

  Updates a key-value store's name and general access level using the provided JSON payload. Returns the updated store object reflecting the applied changes.

• update_queue_requestwrite action

  Updates an existing request in a queue, allowing you to modify its properties or mark it as handled. Setting `handledAt` to the current time removes the request from the head of the queue and releases any lock on it.

• update_request_queuewrite action

  Updates a request queue's name and resource access level by submitting a JSON payload with the desired changes. Returns the full updated request queue object upon success.

• update_runwrite action

  Updates an Actor run's status message and/or general resource access level. Use this to communicate progress to users via the Apify Console UI or to control who can view the run and its associated storages and logs.

• update_taskwrite action
• update_task_inputwrite action

  Updates the input configuration of a specific actor task by merging the provided JSON object with the existing input. Only the properties included in the request body are updated; omitted properties retain their current values.

• update_webhookwrite action

  Updates an existing webhook's configuration by its ID, applying only the properties provided in the JSON request body. Returns the full updated webhook object.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 55% of 866 Scraping and browsing servers

Tools

100

the typical Scraping and browsing server has 6

Tools that change things

54%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 87% of 583 Scraping and browsing servers

Apify: common questions

Is Apify MCP server safe?

Mostly: it is graded B (80/100). Read the Apify safety report

How do I install Apify?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Apify need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Apify maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.5.

What can I use instead of Apify?

Servers from other publishers that do the same job: SeleniumBase MCP server, Browser Use MCP server and Scrapeless MCP server.

How does Apify compare with other Scraping and browsing MCP servers?

safety score 80/100 (higher than 55% of 866 Scraping and browsing servers); tools 100 (the typical Scraping and browsing server has 6); tools that change things 54% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.