Apify MCP server

Purpose: Giving AI agents access to web scraping, data extraction, automation, documentation search, and Actor execution.

Inferred · not functionally tested

Audience: AI agent developers and automation users

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: commercial_oss · license: MIT · platforms: CLI, WEB · deployment: browser, cli, cloud_managed, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: mcp.apify.com · github.com. These links do not verify the individual claims.

Apify MCP server sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: It focuses on giving AI agents access to web scraping, data extraction, automation, documentation search, and Actor execution. Inferred · not functionally tested: It is built as a B2B product for AI agent developers and automation users. Basis unknown · not verified: Apify MCP server is commercial open source (MIT). Basis unknown · not verified: It ships for the web, the command line, and API.

Apify builds and maintains Apify MCP server, and it first shipped in 2025. The project is developed in the open on GitHub with 5k stars and 252 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include actor discovery, actor execution, and result access. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

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