Apify MCP Server — 3,000+ Scrapers at Your AI Agent's Fingertips

Most MCP servers give your agent one capability — search, or database access, or browser automation. The Apify MCP Server takes a different approach: it gives your agent access to an entire marketplace of 3,000+ pre-built scrapers, crawlers, and automation tools (called “Actors” in Apify’s terminology), and lets the agent discover and use new ones on the fly.

Need Amazon product data? There’s an Actor for that. Google Maps leads? Actor. LinkedIn profiles, Instagram posts, TikTok videos, real estate listings? Actors for all of them. The MCP server is the bridge that lets your AI agent search this marketplace, understand what each tool expects, run it, and get structured results back.

What It Does

The Apify MCP Server exposes 17+ tools organized around four capabilities: discovering Actors, running them, accessing stored results, and browsing Apify’s documentation.

Actor Discovery & Execution

Run Management

Storage Access

Documentation

The dynamic tool discovery workflow is the standout feature. Rather than pre-configuring specific scrapers, your agent can:

1. Search the Apify Store for relevant Actors using search-actors
2. Inspect Actor details to understand required inputs via fetch-actor-details
3. Add the Actor as a new tool via add-actor
4. Execute it with appropriate parameters

Each discovered Actor becomes immediately available for use in the conversation. This means your agent’s capabilities grow dynamically based on what it needs, without manual reconfiguration.

Hosted vs Local

Apify offers two ways to run the MCP server, and the differences matter:

The hosted mode at https://mcp.apify.com is the recommended path. It supports OAuth (no token exposure), infers output schemas so agents better understand what they’ll get back, and requires zero local setup. The Apify UI configurator even offers one-click install buttons for supported clients.

SSE deprecated: Server-Sent Events transport was removed on April 1, 2026 as planned, replaced by Streamable HTTP per the MCP specification. If you configured the SSE endpoint (/sse), update to the Streamable HTTP endpoint (/mcp).

Setup

Claude Desktop (hosted with OAuth):

Use the one-click install at mcp.apify.com, or add manually:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_APIFY_TOKEN"
      }
    }
  }
}

(Note: The SSE endpoint /sse was removed April 1, 2026. Use /mcp for Streamable HTTP.)

Claude Desktop (local):

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

Claude Code:

claude mcp add apify -- npx -y @apify/actors-mcp-server

Set APIFY_TOKEN in your environment.

Cursor:

Create .cursor/mcp.json pointing to the hosted URL with Bearer token authentication.

Pricing Reality

The MCP server itself is free and open source (Apache 2.0). But using it costs money because running Actors consumes Apify platform credits:

• Free tier: $5/month in credits (no credit card required). Enough for hundreds of small scraping tasks — testing, learning, small projects.
• Starter: $29/month
• Scale: $39/month+
• Enterprise: Custom pricing

Individual Actor pricing varies widely. Some community Actors are free; premium ones charge per result or per compute unit. Always use fetch-actor-details to check pricing before running an Actor.

The Skyfire integration enables autonomous agent payments via PAY tokens (minimum $5 USD), letting agents pay for Actor runs without pre-configured Apify tokens — interesting for fully autonomous agent workflows.

How It Compares

The Apify MCP Server competes in the web data extraction space. Here’s how it stacks up:

The key differentiator is breadth through marketplace: instead of one general-purpose scraper, you get thousands of purpose-built ones. The tradeoff is quality variance — community-created Actors range from excellent to abandoned, and you need to evaluate each one. Bright Data’s 120+ scrapers are all officially maintained, while Apify’s 3,000+ are community-curated.

In head-to-head stress testing (250 concurrent agents), Bright Data achieved 76.8% success rate vs Apify’s 18.8% — a significant gap for enterprise reliability. But Apify’s per-task speed was competitive (45.9s vs 48.7s), and its marketplace model means there’s likely a specialized Actor for niche sites that general-purpose crawlers can’t handle.

What’s Good

• Unmatched breadth — 3,000+ Actors covering social media, search engines, e-commerce, maps, real estate, and more
• Dynamic tool discovery — agents find and use new scrapers at runtime without configuration changes
• Hosted mode is smooth — OAuth login, no tokens to manage, output schema inference
• Free tier — $5/month in credits with no credit card required, enough for testing and small projects
• Active development — v0.9.16 released March 28, 2026 (4 releases in 8 days after the March 20 v0.9.12); v0.9.16 added x402 payment provider support, renamed Actor tool names to {username}--{actor-name} format, and dedent support for multiline tool descriptions
• Apache 2.0 license — no AGPL concerns for the server itself

What’s Not

• Platform dependency — this is an MCP gateway to a commercial SaaS platform, not a standalone tool. You’re dependent on Apify’s infrastructure, pricing, and continued operation
• Actor quality is uneven — community-created scrapers vary widely in reliability, maintenance, and accuracy. Some are excellent; others are abandoned with broken selectors
• Costs can surprise you — running premium Actors or high-volume scraping burns through credits quickly. A few careless call-actor invocations by an autonomous agent could drain your free tier
• Rate limiting — 30 requests/second per user. Heavy autonomous agent loops can hit this
• Telemetry on by default — both Sentry error tracking and usage telemetry are enabled unless you opt out
• Stress test performance — 18.8% success rate in 250-agent concurrent testing raises questions about reliability under heavy load

The Bottom Line

The Apify MCP Server is the most capable web data extraction gateway available through MCP. Its dynamic tool discovery model — where agents can search a marketplace of 3,000+ scrapers and add them as tools at runtime — is unique and genuinely powerful. No other MCP server offers this level of adaptive capability.

But it’s a gateway to a commercial platform, not a self-contained tool. You’re paying Apify for every Actor run, quality varies across community-created scrapers, and the stress test numbers suggest reliability concerns at scale. For small-to-medium scraping needs with the free tier, it’s an excellent way to give agents structured web data. For enterprise-scale extraction, Bright Data’s officially maintained scrapers and higher reliability may justify the premium.

Rating: 3.5 / 5 — Unique marketplace model with dynamic discovery, held back by platform dependency, uneven Actor quality, and reliability concerns under load. The free tier makes it worth trying; just watch your credit consumption with autonomous agents.

This review was originally published March 23, 2026 and refreshed May 3, 2026. Refresh findings: v0.9.16 (March 28) is current — 4 releases after the March 20 v0.9.12. SSE deprecated April 1, 2026 as planned; Streamable HTTP now required. Stars grew from 945 to ~1,100+. No new CVEs. x402 payment provider added. We research MCP servers thoroughly but do not test them hands-on. Check the GitHub repository for the latest updates.