# apify/actors-mcp-server [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/apify/actors-mcp-server  
**GitHub Stars:** 13425  
**npm Downloads (last month):** 72306  
**Views:** 8  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/apify-actors-mcp-server

## Description
Use 3,000+ pre-built cloud tools, known as Actors, to extract data from websites, e-commerce, social media, search engines, maps, and more

## Tools
Capabilities this server exposes over MCP:

- **title**
- **readOnlyHint**
- **true**
- **get-dataset**
- **fetch-actor-details**
- **apify--web-fetch**
- **apify--website-content-crawler**
- **pageFunction**
- **initialCookies**
- **openWorldHint**
- **call-actor**
- **search-actors**
- **fetch-apify-docs**

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

```json
"mcpServers": {
  "actors-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/actors-mcp-server does

apify/actors-mcp-server exposes Apify Actors as tools that an MCP-compatible AI assistant can discover and invoke. Actors are cloud-based scrapers, crawlers, and automation tools available through the Apify Store. They cover tasks such as extracting Facebook posts, collecting Google Maps contact details, scraping search results, retrieving Instagram data, browsing the web for retrieval-augmented generation, and fetching pages as Markdown, plain text, HTML, or links.

The server is suited to search and data-extraction workflows where the required website or platform is already supported by an Apify Actor. Instead of building a scraper into the agent, the assistant can select an Actor and pass it the task-specific input.

## How it works

The server provides MCP tools for finding and using Actors. An assistant can search the Actor catalog, retrieve Actor metadata, call an Actor, and read the resulting dataset. It also exposes tools for fetching Apify documentation and for using Apify’s web-fetch and website-content-crawler capabilities.

The recommended hosted deployment is available at `https://mcp.apify.com` over streamable HTTP. Clients can authenticate through OAuth or send an `Authorization: Bearer <APIFY_TOKEN>` header. A local stdio deployment is also available through the npm package, which is useful for desktop and command-line MCP clients.

## Setup and configuration

For the hosted option, configure an MCP client with `https://mcp.apify.com`. OAuth-enabled clients can connect using the URL; other configurations can provide an Apify bearer token. The former `/sse` endpoint should not be used because the server now uses streamable HTTP at the URL without the `/sse` suffix.

For a local stdio setup, install or run the package through `npx`:

```bash
npx @apify/actors-mcp-server
```

Set `APIFY_TOKEN` to an Apify API token in the MCP client environment. The command accepts additional options, which can be inspected with `npx @apify/actors-mcp-server --help`. A downloadable MCPB bundle is also available for one-click installation.

## Tools and capabilities

Available capabilities include:

- `search-actors` for locating Actors in the Apify catalog.
- `fetch-actor-details` for inspecting an Actor before running it.
- `call-actor` for starting an Actor with task input.
- `get-dataset` for retrieving data produced by an Actor run.
- `apify--web-fetch` for fetching URL content in formats including Markdown, plain text, HTML, and links.
- `apify--website-content-crawler` for crawling website content.
- `fetch-apify-docs` for accessing Apify documentation through MCP.

The hosted service supports OAuth and features that depend on client capabilities. Actor runs can also be paid through Apify tokens or supported agentic payment methods, including AGI, direct x402 for Pay Per Event Actors, and Skyfire.

## Limitations and notes

Client support for dynamic tool discovery and other MCP features can vary. The hosted service includes features that are unavailable in the local stdio mode, including output-schema inference for structured Actor results. Actor availability, inputs, output shape, runtime, and cost depend on the selected Apify Actor. Local use requires an Apify token unless an applicable hosted payment method is used.

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