Apify

The Apify Model Context Protocol (MCP) server at mcp.apify.com enables your AI agents to 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, allowing you to connect from clients like Claude.ai or Visual Studio Code using just the URL.

🚀 Use the hosted Apify MCP Server!

For the best experience, connect your AI assistant to our hosted server at https://mcp.apify.com. The hosted server supports the latest features - including output schema inference for structured Actor results - that are not available when running locally via stdio.

💰 The server also supports agentic payments via x402 and Skyfire, allowing AI agents to pay for Actor runs without an API token.

Apify MCP Server is compatible with Claude Code, Claude.ai, Cursor, VS Code and any client that adheres to the Model Context Protocol. Check out the MCP clients section for more details or visit the MCP configuration page.

Table of Contents

• 🌐 Introducing Apify MCP Server
• 🚀 Quickstart
• ⚠️ SSE transport deprecation
• 🤖 MCP clients
• 🪄 Try Apify MCP instantly
• 💰 Agentic payments
  • How agentic payments work
  • 💸 x402
  • 🔥 Skyfire
• 🛠️ Tools, resources, and prompts
• 📊 Telemetry
• 💬 Usage examples
• 🐛 Troubleshooting
• ⚙️ Development
• 🔒 Privacy policy
• 🤝 Contributing
• 📚 Learn more

🌐 Introducing Apify MCP Server

The Apify MCP Server allows an AI assistant to use any Apify Actor as a tool to perform a specific task. For example, it can:

• Use Facebook Posts Scraper to extract data from Facebook posts from multiple pages/profiles.
• Use Google Maps Email Extractor to extract contact details from Google Maps.
• Use Google Search Results Scraper to scrape Google Search Engine Results Pages (SERPs).
• Use Instagram Scraper to scrape Instagram posts, profiles, places, photos, and comments.
• Use RAG Web Browser to search the web, scrape the top N URLs, and return their content.

Video tutorial: Integrate 8,000+ Apify Actors and Agents with Claude

🚀 Quickstart

You can use the Apify MCP Server in two ways:

HTTPS Endpoint (mcp.apify.com): Connect from your MCP client via OAuth or by including the Authorization: Bearer <APIFY_TOKEN> header in your requests. This is the recommended method for most use cases. Because it supports OAuth, you can connect from clients like Claude.ai or Visual Studio Code using just the URL: https://mcp.apify.com.

• https://mcp.apify.com streamable transport

Standard Input/Output (stdio): Ideal for local integrations and command-line tools like the Claude for Desktop client.

• Set the MCP client server command to npx @apify/actors-mcp-server and the APIFY_TOKEN environment variable to your Apify API token.
• See npx @apify/actors-mcp-server --help for more options.

You can find detailed instructions for setting up the MCP server in the Apify documentation.

⚠️ SSE transport deprecation on April 1, 2026

Update your MCP client config before April 1, 2026. Apify MCP Server is dropping Server-Sent Events (SSE) transport in favor of Streamable HTTP, in line with the official MCP spec.

Go to mcp.apify.com to update the installation for your client of choice, with a valid endpoint.

🤖 MCP clients

Apify MCP Server is compatible with any MCP client that adheres to the Model Context Protocol, but the level of support for dynamic tool discovery and other features may vary between clients.

To interact with the Apify MCP Server, you can use clients such as Claude Desktop, Visual Studio Code, or Apify Tester MCP Client.

Visit mcp.apify.com to configure the server for your preferred client.

Tested clients

• Claude Desktop
• Claude.ai (web)
• ChatGPT
• VS Code (Genie)
• Cursor
• OpenCode
• Kiro
• Apify Tester MCP Client — designed for testing Apify MCP servers

Smart tool selection based on client capabilities:

When the actors tool category is requested, the server intelligently selects the most appropriate Actor-related tools based on the client's capabilities:

• Clients with dynamic tool support (e.g., Claude.ai web, VS Code Genie): The server provides the add-actor tool instead of call-actor. This allows for a better user experience where users can dynamically discover and add new Actors as tools during their conversation.

• Clients with limited dynamic tool support (e.g., Claude Desktop): The server provides the standard call-actor tool along with other Actor category tools, ensuring compatibility while maintaining functionality.

🪄 Try Apify MCP instantly

Want to try Apify MCP without any setup?

Check out Apify Tester MCP Client

This interactive, chat-like interface provides an easy way to explore the capabilities of Apify MCP without any local setup. Sign in with your Apify account and start experimenting with web scraping, data extraction, and automation tools!

Or use the MCP bundle file (formerly known as Anthropic Desktop extension file, or DXT) for one-click installation: Apify MCP Server MCPB file

💰 Agentic payments

You can pay for Actor runs without an Apify API token using either x402 or Skyfire.

• x402 pays with USDC on Base and does not require a separate platform account. It is fully supported by mcpc (npm install -g @apify/mcpc). We use mcpc because it is one of the few MCP clients that supports the latest features and the x402 protocol natively.
• Skyfire pays with PAY tokens and requires a Skyfire account with a funded wallet. It does not require a special MCP client; the entire payment flow is handled directly through the MCP tool call parameters.

How agentic payments work

Actor run costs vary, so both payment methods use a prepaid balance model. The payment flow happens in four steps:

1. Discovery: The agent discovers Actors with search-actors or fetch-actor-details. Those calls are free.
2. Prepayment: Before running a paid Actor tool, the agent funds a prepaid balance.
   • x402: mcpc automatically signs a $1.00 USDC transaction.
   • Skyfire: The agent creates a PAY token (minimum $5.00) using Skyfire's create-pay-token tool.
3. Execution: The agent calls the Actor tool.
   • x402: Handled automatically by mcpc using the prepaid balance.
   • Skyfire: The agent explicitly passes the PAY token in the skyfire-pay-id input property.
4. Resolution: The tool returns the Actor results. Unused funds stay available for later runs.
   • x402: After 60 minutes of inactivity, the server refunds any unused balance to the wallet on Base.
   • Skyfire: Skyfire returns unused funds when the token expires.

💸 x402

The x402 protocol enables direct, machine-to-machine payments. Your MCP client can use it to pay for Actor runs with USDC on the Base blockchain, completely bypassing the need for an Apify API token.

Prerequisites

• A wallet with USDC on Base mainnet.

Setup

Create or import a wallet:

# Create a new wallet
mcpc x402 init

# Import an existing wallet
mcpc x402 import <private-key>

# Show the wallet address so you can fund it with USDC on Base (https://base.org)
mcpc x402 info

Connect to the server with x402 enabled:

mcpc connect "mcp.apify.com?payment=x402" @apify --x402

You can now call a paid tool:

mcpc @apify tools-call call-actor actor:="apify/rag-web-browser" input:='{"query": "latest AI news"}'

🔥 Skyfire

Skyfire provides managed payment infrastructure for AI agents. Instead of authenticating with an Apify API token, your agent passes a Skyfire payment token to cover the cost of each tool call using PAY tokens.

Prerequisites

• A Skyfire account with a funded wallet.
• An MCP client that supports multiple servers, such as Claude Desktop, OpenCode, or VS Code.

Setup

Configure the Skyfire MCP server and the Apify MCP Server in your client. Add payment=skyfire to the Apify server URL:

{
  "mcpServers": {
    "skyfire": {
      "url": "https://api.skyfire.xyz/mcp/sse",
      "headers": {
        "skyfire-api-key": "<YOUR_S

…