Apify
Let agents trigger Apify actors to scrape sites, harvest lists, and run cloud automation while you validate niches or feed build pipelines.
Overview
com.mcparmory/apify is an MCP server for the Idea phase that lets agents build, deploy, and run Apify web scraping and automation actors in the cloud.
What is this MCP server?
- Build, deploy, and run Apify web scraping and automation actors from agent-driven workflows.
- Stdio MCP distribution via uvx (mcparmory-apify) or Docker image ghcr.io/mcparmory/apify:1.0.5.
- Cloud execution model so heavy crawls stay off the laptop while the agent orchestrates runs.
- Registry entry com.mcparmory/apify version 1.0.5 sourced from mcparmory/registry on GitHub.
- Fits agent-tooling stacks when you need structured web data without writing bespoke scrapers per site in every session.
- Server version 1.0.5 with dual PyPI (mcparmory-apify) and OCI package
- Stdio transport on all published packages per server.schema.json
Community signal: 25 GitHub stars.
What problem does it solve?
Research workflows stall when every new site means custom scrape scripts the agent cannot execute or monitor in one place.
Who is it for?
Solo builders doing competitive research, directory mining, or dataset collection who already use Apify and want MCP control from Claude Code or Cursor.
Skip if: One-off page reads where browser MCP or manual copy suffices, or projects that cannot use third-party cloud scraping accounts.
What do I get? / Deliverables
After setup, your agent can drive Apify actors through MCP for repeatable web automation and structured extracts during discovery and validation.
- Agent-invokable Apify actor build, deploy, and run operations
- Cloud-backed scraping runs wired into agent sessions
Recommended MCP Servers
Journey fit
Scraping and actor runs most often support early discovery—competitor pages, directories, and public datasets—before committing to a full product architecture. Apify MCP bridges the agent to deployed actors in the cloud, which is research and data-gathering work rather than in-app UI polish.
How it compares
Cloud actor orchestration MCP, not a local headless browser skill or static dataset download.
Common Questions / FAQ
Who is com.mcparmory/apify for?
Builders and developers using AI agents who rely on Apify for scraping and automation and want those capabilities exposed as MCP tools.
When should I use com.mcparmory/apify?
Use it in Idea or early Validate when you need agents to run or manage Apify actors for competitor research, list building, or automation prototypes.
How do I add com.mcparmory/apify to my agent?
Add the stdio server to your MCP config with uvx mcparmory-apify or ghcr.io/mcparmory/apify:1.0.5, provide your Apify API token, and reload the agent.