WEB EXTRACTION AND AUTOMATION / Apify
Apify MCP Server
Searches Apify Store and runs Apify Actors (scrapers, crawlers and automation tools) from an MCP client, through Apify's hosted endpoint or a local stdio package.
“Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store”
01 / THE REASONING
Why this made the selection.
- Published in Apify's own repository; the README at this commit documents the hosted Streamable HTTP endpoint https://mcp.apify.com, with OAuth or a bearer token, and a stdio package run as npx @apify/actors-mcp-server.
- The README lists the tools the hosted server allows without a token (search-actors, fetch-actor-details, search-apify-docs, fetch-apify-docs, apify-api-search, apify-api-details), and LICENSE.md is MIT, Copyright (c) 2025 Apify.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md at 99c97efa4009a15f0cea839d4eea40e9fcd268f3
- LICENSE.md at the same commit
- package.json at the same commit
- server.json at the same commit
Our findings
- The README says the legacy https://mcp.apify.com/sse endpoint has been removed in favour of Streamable HTTP.
- Rental Actors are available only through the hosted server; a local stdio server can use only Actors already in its toolset.
- The README documents agentic payments (AGI tokens, direct x402 in USDC on Base, Skyfire PAY tokens) as alternatives to an Apify API token.
Not established by this review
- npx launch
- The hosted endpoint or OAuth flow
- Any Actor run or payment flow
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx @apify/actors-mcp-server Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- The README sets the client's server command to the line above, with APIFY_TOKEN in the environment. It was not run.
- Remote-capable clients can instead connect to https://mcp.apify.com and sign in with OAuth. Do not commit the token.
Before you start
- Node.js with npx
- An Apify API token, or an OAuth sign-in on the hosted server
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Apify MCP README ↗Checked
https://github.com/apify/apify-mcp-server/blob/99c97efa4009a15f0cea839d4eea40e9fcd268f3/README.md
Supports: Hosted and stdio setup, Unauthenticated tools, Private hosted-server repository, Telemetry, Agentic payments
- Apify MCP LICENSE.md ↗Checked
https://github.com/apify/apify-mcp-server/blob/99c97efa4009a15f0cea839d4eea40e9fcd268f3/LICENSE.md
Supports: MIT License, Copyright (c) 2025 Apify
- Apify MCP package.json ↗Checked
https://github.com/apify/apify-mcp-server/blob/99c97efa4009a15f0cea839d4eea40e9fcd268f3/package.json
Supports: Package @apify/actors-mcp-server 0.18.1, License MIT
- Apify MCP server.json ↗Checked
https://github.com/apify/apify-mcp-server/blob/99c97efa4009a15f0cea839d4eea40e9fcd268f3/server.json
Supports: Description, Remote endpoint identity