mewcp-apify MCP Server

A Model Context Protocol (MCP) server that exposes Apify's API for running Actors, managing runs, and retrieving scraped datasets.

Local server

What is the mewcp-apify MCP Server?

mewcp-apify is an MCP project maintained in the asthetech/mewcp-apify repository. The maintainer describes its purpose as “A Model Context Protocol (MCP) server that exposes Apify's API for running Actors, managing runs, and retrieving scraped datasets”. Read the project documentation for the complete scope.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
my_only	boolean, optional) — Only return Actors owned by you (default: true)
limit	integer, optional) — Maximum number of tasks to return, 1–1000 (default: 100)
offset	integer, optional) — Number of tasks to skip for pagination (default: 0)
actor_id	string, required) — Actor ID to run (e.g. 'username~actor-name' or Actor ID)
input_data	string, optional) — JSON string of input data for the Actor (default: '{}')
timeout_secs	integer, optional) — Run timeout in seconds
memory_mbytes	integer, optional) — Memory limit in MB (min 128)
build	string, optional) — Build tag or number (default: 'latest')
run_id	string, required) — Actor run ID
wait_for_finish	integer, optional) — Seconds to wait for run completion, 0–60 (default: 0)
status	string, optional) — Filter by status: 'SUCCEEDED', 'FAILED', 'RUNNING', 'ABORTED', etc.
dataset_id	string, required) — Dataset ID (returned in the Actor run response)
clean	boolean, optional) — Remove hidden fields starting with '' (default: true)