Apify MCP server

Purpose: Connecting AI agents to web scraping, data extraction, and automation tools without building each integration.

Inferred · not functionally tested

Audience: developers building AI agents and automation workflows

Inferred · not functionally tested

Functions: agents, data_extraction, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: MIT · platforms: CLI, WEB · deployment: browser, cli, cloud_managed, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: unknown.

In the Frameworks & runtimes space, Apify MCP server takes a focused approach. Inferred · not functionally tested: It focuses on connecting AI agents to web scraping, data extraction, and automation tools without building each integration. Inferred · not functionally tested: It is built as a B2B product for developers building AI agents and automation workflows. Basis unknown · not verified: It ships for the web, the command line, and API.

Behind Apify MCP server is Apify, and it first shipped in 2025. Development happens publicly on GitHub with 7.3k stars and 234 commits in the last 90 days. It competes in a saturated segment with 25 similar projects in PulseGate's index. Inferred · not functionally tested: Among its 6 catalogued features are MCP server access, actor execution, and web scraping. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.