This server connects AI assistants to the Apify platform using the Model Context Protocol, enabling agents to discover and execute web scraping and automation Actors. It routes user requests and Actor inputs to the external Apify API for execution and returns structured data or markdown content.
Project overview
Provides dynamic tool discovery that allows an AI agent to search the Apify Store for new Actors and incorporate them as tools during runtime.
Project type
MCP
Deployment
Refer to project documentation
License
MIT
Best for
Developers and AI engineers building agents that need to interact with web scrapers and automation tools via the Apify Store.
Key capabilities
Loads an Apify Actor's input schema and creates a corresponding MCP tool for the LLM to use.
Allows an AI agent to search for new Actors in the Apify Store, view their details, and incorporate them dynamically.
Access data from Apify datasets and key-value stores, retrieve items, and manage metadata.
Retrieve lists of Actor runs, inspect details, retrieve logs, and abort runs.
Supports automated machine-to-machine payments for Actor runs via x402 and Skyfire.
Supports OAuth allowing connection from clients like Claude.ai or VS Code using just a URL.
Server is pre-configured with the apify/rag-web-browser Actor by default to search the web and return markdown content.
Provides tools to search Apify documentation and fetch specific documents for AI context.
Limitations and risks
Actor input schema processing involves truncating descriptions to 500 characters and enum fields to 2000 characters.
Rental Actors are only available on the hosted MCP server, not when running locally via stdio.
The server does not yet provide any resources.
The default tools configuration may change in future versions; production use requires explicit specification.
User requests and Actor inputs are sent to the external Apify API for execution.
The default tools configuration may change in future versions, which may impact production stability without explicit tool specification.
Getting started
Set up is rated easy. Configure the MCP client with the hosted server URL or a local npx command. An Apify API token is required if not using x402, Skyfire, or OAuth.
Alternatives and comparisons
Selects and maintains stable access methods for various internet platforms to help agents read and search the web without API fees.