← Back to directory
A

Apify MCP Server

Official
Turn thousands of Apify Actors into AI-agent tools for web scraping and data extraction.
Category
Other #42 of 230
Stars
★ 14.6k Very popular
Transport
Streamable HTTP · stdio (local process)
Runtime
Hosted (no local runtime) · Node.js 22+
Credentials
Optional API key
License
MIT
Last commit
Tools
19
64FMRS · C

Officially maintained by Apify, this MCP server exposes thousands of Apify Store Actors as callable AI-agent tools, supporting both a hosted streamable-http endpoint (OAuth or Bearer token) and a local stdio mode. It covers Actor discovery, execution, run management, and storage access, but requires an Apify account/token, incurs run costs, and collects telemetry by default.

Strongest · Documentation 17/20 Weakest · Security and permissions 8/20

Reliability
10/20
Security and permissions
8/20
Maintenance
15/20
Documentation
17/20
Setup experience
14/20
Why each score
Reliability 10/20
server.json clearly defines a streamable-http remote endpoint with a required Authorization header, and the README's tool list, default tool set (actors, docs, apify/rag-web-browser), and auto-injection rules (call-actor/Actor tools/get-actor-run triggering get-dataset-items, etc.) are internally consistent with no obvious contradictions. However, this is a static-only review and the provided material contains no verifiable test files or CI workflow contents (the README only names a badge and a check.yaml file, without evidencing its content). Per the static calibration rule, reliability is capped at 12. Score: 10.
Security and permissions 8/20
The manifest marks the Authorization token as isSecret and isRequired, showing reasonable baseline credential handling. However, the default tool set includes call-actor and Actor tools with openWorldHint (executing arbitrary third-party Apify Actors with real external network access and side effects such as scraping and incurred cost), and the README documents optional agentic payment flows (x402/Skyfire/AGI) where, for example, the x402 flow has the client 'automatically sign a $1.00 USDC transaction' to fund a prepaid balance, with no explicit per-spend confirmation step described beyond ordinary MCP tool-call approval. Telemetry is also enabled by default (opt-out only). These are visible but incompletely scoped/confirmed risks; they do not rise to an unmitigated red line since payment features are opt-in, capped in amount, and refundable, and open-world execution is disclosed via openWorldHint for client-side gating. Score: 8.
Maintenance 15/20
The project is MIT-licensed, versioned at 0.14.2, has CONTRIBUTING.md and DEVELOPMENT.md, a defined contribution policy and canary pre-release process, and is distributed via Docker Hub through the community-maintained mcp-registry (README itself notes deployment frequency there is 'unknown'). The repo is not archived, and 2605 stars with 110 open issues indicate active usage. No explicit security-response channel or SECURITY.md is evidenced in the provided material. Score: 15.
Documentation 17/20
The README is extensive: table of contents, a tool overview table with a default-enablement legend, tools configuration (URL query params and CLI flags), backward-compatibility notes, disclosed limitations (schema truncation rules, etc.), a privacy policy, telemetry opt-out instructions, and a troubleshooting link. Gaps include no concrete per-Actor cost figures (only 'costs vary'), and payment-flow fee/token-lifetime details are deferred to an external link not included in the provided material. Score: 17.
Setup experience 14/20
Two clear setup paths are documented: the hosted OAuth endpoint ('just the URL') and local npx with APIFY_TOKEN, plus JSON config examples, CLI flag examples, a one-click MCPB installer, and a list of tested clients — overall steps are clear. As this is a static review, the provided material contains no verifiable CI or test evidence confirming the connection flow actually works end-to-end, so per the static calibration rule setup is capped at 15. Score: 14.

Static review · not runListed 2026-08-06

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Developers adding web scraping/data extraction capabilities to AI agents without building their own crawlers
  • Users of Claude, Cursor, VS Code, or ChatGPT who want dynamic discovery and use of Apify Store scraping tools
  • Autonomous agents that need to pay per Actor run via prepaid tokens (AGI, x402, or Skyfire)

Not for

  • Tasks that don't need internet scraping, such as pure local filesystem or database work
  • Users without an Apify account who are unwilling to authenticate via OAuth or API token
  • Fully offline setups that must avoid sending any data to the Apify platform

Required permissions

  • Requires an Apify API token (Bearer) or OAuth login to an Apify account
  • Runs Actors and reads run status, dataset, and key-value store data on behalf of the user's account
  • Needs outbound network access to reach the Apify API and the external websites Actors scrape

Risks and side effects

  • Running Actors incurs cost, paid via prepaid balance, AGI, direct x402, or Skyfire
  • Telemetry (tool-call usage data) is collected by default, and stdio mode also enables Sentry error tracking by default unless opted out
  • Dynamic tool discovery lets the agent invoke arbitrary third-party Actors from Apify Store, whose behavior and data handling are outside this server's control
  • Scraped website data passes through the Apify API; users are responsible for ensuring scraping complies with target sites' terms of service

Setup

Before you start

Runtime:Hosted (no local runtime) · Node.js 22+

APIFY_TOKEN optionalsecret Apify platform API token used to authenticate against the hosted server or local stdio run; available in your Apify account settings.
Other optional settings (3)
TELEMETRY_ENABLED optional Set to false to disable telemetry and Sentry error tracking when running the local stdio server.
UI_MODE optional Set to true to enable MCP Apps widget rendering in tool responses (also available via CLI flag).
APIFY_META_ORIGIN optional Environment variable used when running the server locally for development (e.g., STANDBY), together with apify run.

Hosted (recommended): connect an OAuth-capable client (e.g. Claude.ai, VS Code) directly to the URL https://mcp.apify.com, or include an Authorization: Bearer <APIFY_TOKEN> header in requests; note the legacy /sse endpoint has been removed, so drop the /sse suffix and use the streamable-http URL. Local (stdio): set the MCP client's server command to npx @apify/actors-mcp-server and set the APIFY_TOKEN environment variable to your Apify API token; run npx @apify/actors-mcp-server --help for more options. A one-click .mcpb bundle install file is also available from the latest GitHub release.

claude_desktop_config.json
{"mcpServers":{"apify":{"url":"https://mcp.apify.com","headers":{"Authorization":"Bearer <APIFY_TOKEN>"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "apify": {
      "url": "https://mcp.apify.com",
      "headers": {
        "Authorization": "Bearer <APIFY_TOKEN>"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http apify https://mcp.apify.com --header 'Authorization: Bearer <APIFY_TOKEN>'

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

After connecting to https://mcp.apify.com, tools like search-actors, fetch-actor-details, call-actor, and apify--rag-web-browser should appear in the client's tool list; calling search-actors for any Actor proves the connection works.

Troubleshooting

  1. Confirm APIFY_TOKEN is set correctly (local stdio) or OAuth authorization completed (hosted)
  2. Confirm you are not using the removed `/sse` endpoint — use `https://mcp.apify.com` instead
  3. For local development, confirm Node.js v22+ is installed and `pnpm run build` has been run
  4. Use MCP Inspector against `http://localhost:3001` (HTTP mode) or `./dist/stdio.js` (stdio mode) to debug
  5. Check the `tools` query parameter/CLI flag configuration, since default tool sets may change in future versions
  6. Disable telemetry/Sentry reporting with `--telemetry-enabled=false` or `TELEMETRY_ENABLED=false` if needed

Things to try

Once connected, you can ask your AI assistant things like:

  • Use apify--rag-web-browser to find the latest news about autonomous AI agents and summarize the key points.
  • Search Apify Store for a Google Maps email extractor and show me its input parameters.
  • Scrape the top 10 restaurants in Prague from Google Maps with their contact details.
  • List my recent Actor runs and fetch the log of the latest one.

Tools 19

search-actors read-only
Search for Actors in Apify Store.
fetch-actor-details read-only
Retrieve detailed information about a specific Actor, including its input schema, README (summary when available, full otherwise), pricing, and output schema.
call-actor writes
Call an Actor and get its run results. Use fetch-actor-details first to get the Actor's input schema.
get-actor-run read-only
Get detailed information about a specific Actor run.
get-dataset-items read-only
Retrieve items from a dataset with support for filtering and pagination.
get-key-value-store-record read-only
Get the value associated with a specific key in a key-value store.
abort-actor-run destructive
Abort a running Actor run, optionally gracefully.
search-apify-docs read-only
Search the Apify documentation for relevant pages.
Show 11 more tools
fetch-apify-docs read-only
Fetch the full content of an Apify documentation page by its URL.
apify--rag-web-browser writes
A pre-configured Actor tool used to browse the web, search, and return top-result content.
report-problem writes
Report a problem with an Apify tool or Actor to the Apify team.
get-actor-run-list read-only
Get a list of an Actor's runs, filterable by status.
get-actor-log read-only
Retrieve the logs for a specific Actor run.
get-dataset read-only
Get metadata about a specific dataset.
get-dataset-schema read-only
Generate a JSON schema from dataset items.
get-key-value-store read-only
Get metadata about a specific key-value store.
get-key-value-store-keys read-only
List the keys within a specific key-value store.
get-dataset-list read-only
List all available datasets for the user.
get-key-value-store-list read-only
List all available key-value stores for the user.

Use cases

Scrape posts from Facebook pages/profiles
Extract contact details from Google Maps listings
Scrape Google Search Engine Results Pages (SERPs)
Scrape Instagram posts, profiles, places, photos, and comments
Search the web and retrieve top-result content with RAG Web Browser

Supported clients

Claude Desktop
Claude.ai
Claude Code
Cursor
VS Code
ChatGPT
OpenCodePartial support
KiroPartial support
Apify Tester MCP Client

Listed from the project's documentation, not tested by this site.

Overview

The Apify MCP Server (mcp.apify.com) lets AI agents extract data from social media, search engines, maps, e-commerce sites, and any other website using thousands of ready-made scrapers, crawlers, and automation tools from Apify Store. It supports OAuth login and Bearer-token authentication (Authorization: Bearer <APIFY_TOKEN>), so clients like Claude.ai or VS Code can connect using just the hosted URL, or it can be run locally over stdio via npx @apify/actors-mcp-server.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 672 · Tools 11 Compare with this →

Source revision 17e1e61cc336 Data synced 2026-11-04 Read the FMRS scoring method