MCP Apify
Related Servers
Alternatives to MCP Apify
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables web scraping, browser automation, and dataset management through Apify's actor platform.MIT
- 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.32,599 npmMIT

kanto-labs-mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to run pay-per-result web data and media tools such as website tech stack detection, document-to-Markdown conversion, SEO audits, OCR, and domain lookups via Apify.14MIT- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to use thousands of Apify Actors for web scraping, data extraction, and automation via the Model Context Protocol.-
- 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
- AlicenseNot gradedqualityCmaintenanceEnables running Apify Actors for web scraping and automation, fetching dataset results, and scraping URLs to clean markdown via MCP.215 npm1MIT
TDQS
Scored across 28 tools
Most tools are clearly distinct by resource (actor, dataset, run, etc.) and action (get, list, run), but some overlap exists, such as get_run_dataset_items and get_dataset_items, which could cause confusion about which to use for dataset access. The descriptions help clarify, but the boundaries between run-specific and general dataset tools are not perfectly sharp.
Tool names follow a highly consistent verb_noun pattern throughout, with verbs like get, list, run, abort, and resurrect applied predictably to nouns like actor, dataset, run, etc. There are no deviations in style or convention, making the naming scheme clear and systematic.
With 28 tools, the count feels heavy for the domain of managing Apify actors, datasets, runs, and related resources. While it covers many operations, it may be overwhelming for agents, as some tools could be consolidated or omitted without losing functionality, such as having multiple get_* variants that might be redundant in practice.
The tool set provides comprehensive CRUD and lifecycle coverage for the Apify domain, including operations for actors, datasets, key-value stores, runs, schedules, and tasks. It supports creation (run_actor, run_task), retrieval (get_*, list_*), updates (resurrect_run), and deletion (abort_run), with no obvious gaps that would hinder agent workflows.