Give your AI agent a wallet and 8,000 web scrapers
It turns Apify's marketplace of scrapers and automation tools into MCP tools that AI agents can discover, run, and pay for autonomously.

What it does
The Apify MCP Server bridges Model Context Protocol clients—like Claude, Cursor, or VS Code—to the Apify Store. It lets an AI assistant treat any Apify Actor (a containerized scraper or automation job) as a callable tool, so the agent can extract data from social media, search engines, maps, or e-commerce sites without writing its own crawler. A hosted endpoint at mcp.apify.com handles OAuth connections, while a local stdio transport is available for desktop integrations.
The interesting bit The standout feature is agentic payments: the server can charge AI agents for Actor runs via x402 (USDC on Base) or Skyfire, using prepaid balances that refund unused funds. It effectively gives your agent its own petty-cash account for web scraping, removing the need for a human-managed API token entirely.
Key highlights
- Exposes thousands of Apify Store Actors—Facebook scrapers, Google Maps extractors, Instagram crawlers, and more—as dynamically discoverable MCP tools.
- Hosted endpoint supports OAuth and streamable HTTP transport; the older SSE transport is deprecated and will be removed on April 1, 2026.
- Agentic payment support via x402 (USDC on Base) and Skyfire (PAY tokens) lets agents prepay for runs and receive automatic refunds of unused balances.
- The hosted version infers output schemas for structured Actor results, a feature not available in the local stdio mode.
- Compatible with Claude Desktop, Claude.ai, Cursor, VS Code, ChatGPT, OpenCode, and Kiro.
Caveats
- SSE transport is deprecated and will be removed on April 1, 2026, so existing configs will need updating.
- Dynamic tool discovery and feature support vary depending on the MCP client you use.
- The local stdio mode lacks hosted-only features like output schema inference.
Verdict Worth a look if you’re building AI agents that need real-world web data and would rather rent battle-tested scrapers than maintain your own. Skip it if your data sources already offer clean APIs and you don’t want to explain blockchain micropayments to your finance team.
Frequently asked
- What is apify/apify-mcp-server?
- It turns Apify's marketplace of scrapers and automation tools into MCP tools that AI agents can discover, run, and pay for autonomously.
- Is apify-mcp-server open source?
- Yes — apify/apify-mcp-server is open source, released under the MIT license.
- What language is apify-mcp-server written in?
- apify/apify-mcp-server is primarily written in TypeScript.
- How popular is apify-mcp-server?
- apify/apify-mcp-server has 2.2k stars on GitHub and is currently cooling off.
- Where can I find apify-mcp-server?
- apify/apify-mcp-server is on GitHub at https://github.com/apify/apify-mcp-server.