# apify-mcp-server [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/apify/apify-mcp-server  
**GitHub Stars:** 15336  
**npm Downloads (last month):** 110060  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/apify-mcp-server

## Description
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

## Tools
Capabilities this server exposes over MCP:

- **search-actors** — Search for Actors in Apify Store.
- **fetch-actor-details** — Get an Actor's input schema, README (summary when available, full otherwise), pricing, and a Server Actor's HTTP operations. The output schema is opt-in.
- **call-actor** — Run an Actor and return its run status and storage IDs. Use `fetch-actor-details` first to get the input schema.
- **fetch-actor-mcp-tool-list** — List the tools of an Actor that runs an MCP server, with their schemas, annotations, and metadata.
- **call-actor-mcp-tool** — Call one tool on an Actor's MCP server and return its result.
- **send-server-actor-request** — Send one HTTP request to a Server Actor's API, as documented by its API schema, and return the response.
- **get-actor-run** — Get details about an Actor run.
- **get-dataset-items** — Read items from a dataset, with filtering and pagination.
- **get-key-value-store-record** — Get the value stored under a key in a key-value store.
- **abort-actor-run** — Abort a running Actor run, optionally gracefully.
- **search-apify-docs** — Search the Apify and Crawlee documentation for relevant pages.
- **fetch-apify-docs** — Fetch the full content of a documentation page by its URL.
- **report-problem** — Report a problem with an Apify tool or Actor to the Apify team.
- **get-actor-list** — List the Actors you own and those shared with you, including private ones.
- **delete-actor** — Delete an Actor from your account permanently. Public Actors must be unpublished first.
- **get-actor-run-list** — List Actor runs, filtered by Actor and status.
- **get-actor-run-log** — Read the log of an Actor run.
- **get-dataset** — Get metadata about a dataset.
- **get-dataset-schema** — Generate a JSON schema from dataset items.
- **get-dataset-list** — List the datasets in your account.
- **get-key-value-store** — Get metadata about a key-value store.
- **get-key-value-store-keys** — List the keys in a key-value store.
- **get-key-value-store-list** — List the key-value stores in your account.
- **create-actor-task** — Create a saved Actor task (a named, reusable Actor configuration).
- **get-actor-task** — Get a saved Actor task, its publication state, and its public display configuration.
- **update-actor-task** — Update a task's input, run options, or public display configuration.
- **publish-actor-task** — Publish a task on its public landing page.
- **unpublish-actor-task** — Unpublish a task from its public landing page.
- **create-schedule** — Create a schedule that runs Actors or tasks on a cron expression.
- **get-schedule** — Get a schedule, its cron expression, state, and the actions it runs.
- **update-schedule** — Update a schedule's cron expression, time zone, enabled state, or actions.
- **delete-schedule** — Delete a schedule.
- **build-actor** — Build an Actor version and wait a bounded time for the build to finish.
- **get-actor-build** — Get the status of an Actor build.
- **get-actor-build-list** — List the account's builds, or one Actor's, in every status, newest first.
- **get-actor-build-log** — Read the log of an Actor build.
- **get-actor-version** — Get an Actor version's file listing with hashes, plus the content of the files you ask for.
- **create-actor** — Create a private Actor in your account from files, optionally starting a build.
- **update-actor-version** — Write, edit, or delete files of an Actor version in one all-or-nothing write.
- **create-actor-version** — Add a version to an Actor, from files or as a copy of another version, optionally starting a build.
- **delete-actor-version** — Delete an Actor version. Its builds and their tags stay.
- **apify-api-search** — Search the Apify API reference by keywords. Returns each operation's method, path, and docs page.
- **apify-api-details** — Get the parameters and request body schema of the Apify API operations on a path.
- **apify-api-read** — Send a GET request to an Apify API path, like `apify api` in the Apify CLI. It refuses GETs to the synchronous run endpoints, which start a paid run.
- **apify-api-write** — Send a POST, PUT, PATCH, or DELETE request with a JSON body to any Apify API path, like `apify api` in the Apify CLI.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "apify-mcp-server": {
    "command": "npx",
    "args": ["-y","@apify/actors-mcp-server"],
    "env": {
      "APIFY_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `APIFY_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What apify-mcp-server does

apify-mcp-server gives MCP clients access to Apify Store Actors and Apify account operations. Actors are ready-to-run tools for activities such as fetching web pages, monitoring search results, generating leads, enriching data, and collecting information from e-commerce or social platforms. The agent can search the Store, inspect an Actor before using it, run the Actor, and retrieve its output.

The server also supports Actors that expose their own MCP tools and Server Actors with HTTP APIs. Beyond execution, it covers run inspection, datasets, key-value stores, saved Actor tasks, schedules, and selected Actor administration. It can search and retrieve Apify and Crawlee documentation as well.

## How it works

A typical workflow starts with `search-actors`, followed by `fetch-actor-details` to obtain the Actor's input schema, README content, pricing, and, for Server Actors, documented HTTP operations. The client then uses `call-actor` with the appropriate input. That call returns run status and storage identifiers, which can be used with dataset or key-value-store tools to read the results.

For an Actor that runs an MCP server, `fetch-actor-mcp-tool-list` exposes its available tools and schemas before `call-actor-mcp-tool` invokes one. Server Actors can instead receive an HTTP request through `send-server-actor-request`. Run logs, status, cancellation, datasets, and stored records are available through separate tools.

## Setup and configuration

The hosted endpoint is `https://mcp.apify.com`. Configure it in an MCP client that supports remote servers and authenticate with Apify through OAuth. If the client cannot use OAuth, send an Apify API token as an `Authorization: Bearer <APIFY_TOKEN>` header. Keep the token out of source repositories.

For local use, install or run the `@apify/actors-mcp-server` npm package through `npx`. Local stdio execution requires Node.js 22 or later and uses the `APIFY_TOKEN` environment variable. A token saved through `apify login` can also be read by the local server. The Apify MCP configurator generates client-specific configuration, and the Apify CLI can install configuration for supported clients such as Cursor, Claude Code, VS Code, and Codex.

## Tools and capabilities

- Search Apify Store Actors and inspect their schemas, pricing, documentation, and output schema when requested.
- Run Actors, check run status, read logs, list runs, and abort active runs.
- Discover and invoke tools exposed by Actors that run MCP servers.
- Send documented HTTP requests to Server Actors.
- Read dataset metadata and items with filtering and pagination, and generate a JSON schema from dataset contents.
- Inspect key-value stores, list their keys, and retrieve stored values.
- List, create, update, publish, and unpublish saved Actor tasks.
- Create and inspect schedules that run Actors or tasks on cron expressions.
- Search and fetch Apify and Crawlee documentation.
- List or delete Actors in the connected account, and report problems to the Apify team.

## Limitations and notes

Actor execution and result handling depend on the selected Actor's input schema, storage output, and API behavior. Fetch the Actor details before calling it so the client can construct valid input. Deleting an Actor is permanent, and public Actors must be unpublished before deletion. Authentication is required for the hosted or local connection, using OAuth or an Apify API token depending on the client setup.

_Full upstream README: https://allmcps.com/mcp/apify-mcp-server/readme_