Apify MCP Server
Related Servers
Alternatives to Apify MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGives AI agents access to thousands of ready-made Apify Store Actors, letting them search for a tool, inspect its input and pricing, run it, and read back structured results for web scraping, data extraction, and browser automation. It can be used as a hosted endpoint with OAuth or run locally over stdio.42,948 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceExposes over 19,000 Apify Actors as MCP tools for web scraping, data extraction, and OSINT automation. It enables AI agents to dynamically discover and execute scrapers to collect structured data and crawl web content.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to use thousands of Apify Actors for web scraping, data extraction, and automation via the Model Context Protocol.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to use Apify Actors as tools to perform specific tasks like web scraping, data extraction, and searching across various platforms through the Model Context Protocol.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to thousands of Apify Actors for web scraping, data extraction, and automation tasks, with dynamic tool discovery to find and use any Actor from the Apify Store in real time.42,948 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with the Apify platform to manage actors, monitor runs, and retrieve scraped data from datasets. It supports natural language commands for executing web scrapers, managing tasks, and accessing key-value stores.28MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct role: Store discovery, Actor details, Actor execution, run inspection, dataset retrieval, key-value retrieval, aborting runs, docs search/fetch, and problem reporting. The only near-pairs (search-actors vs. search-apify-docs, fetch-actor-details vs. fetch-apify-docs) are explicitly separated by domain and usage guidance.
All tool names use consistent kebab-case with a verb-first pattern such as search-actors, fetch-actor-details, get-actor-run, and abort-actor-run. The convention is predictable throughout the set.
Ten tools is well-scoped for an Apify MCP server covering discovery, execution, result retrieval, documentation, and support. Each tool earns its place without obvious redundancy.
The surface covers the core lifecycle: find Actors, inspect them, run them, check runs, retrieve outputs, abort runs, and consult docs. Minor gaps exist around listing runs/datasets/key-value stores or broader storage management, but agents can work around these with known IDs.