Apify MCP server

Purpose: Connecting AI agents to web scraping, data extraction, and automation tools.

Inferred · not functionally tested

Audience: developers building AI agents and automation workflows

Inferred · not functionally tested

Functions: agents, data_extraction, browser_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, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: unknown.

Apify MCP server sits in PulseGate's Frameworks & SDKs category. Inferred · not functionally tested: It focuses on connecting AI agents to web scraping, data extraction, and automation tools. Inferred · not functionally tested: It is built as a B2B product for developers building AI agents and automation workflows. Basis unknown · not verified: It runs on the web, the command line, and API.

It is developed by Apify, and it first shipped in 2025. Development happens publicly on GitHub with 7.3k stars and 234 commits in the last 90 days. The category is crowded — PulseGate's index counts 25 comparable projects. Inferred · not functionally tested: Key capabilities include 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.