Run and manage Apify actors for web scraping, browser automation and data extraction. Execute scalable automation workflows and collect structured data from the web.
DeepSeek Harness (DSH) is DeepSeek's agent harness. Each MCP server is one plugin entry in your project config.
This guide connects Apify to DeepSeek Harness through MewCP, so DeepSeek Harness can use Apify's 7 tools, like apify_list_actors, apify_run_actor and apify_get_run, without your Apify credentials ever reaching the app.
Your Apify API key is stored encrypted and injected only at call time. Your agent never holds it, so it can never leak it, log it or paste it into a prompt.
More apps
Crawl websites and extract clean structured data optimized for AI applications and automation. Collect content from the web at scale while maintaining high-quality outputs.
Extract structured data from websites and public web pages. Fetch content, parse information and transform online data into formats that can be consumed by applications, agents and workflows.
TinyFish MCP for running AI-driven browser automation tasks, deep web research, persistent browser login profiles, remote CDP browser sessions, and agentic wallet payments.
Scrape, extract, and understand the web, plus identify any company from a domain, email, name, or transaction string. This MCP server exposes Context.dev's API for web scraping in multiple formats (raw HTML, Markdown, screenshots, images, sitemaps, and web search), schema-driven structured data extraction, design-system extraction (styleguides and fonts), and brand intelligence lookups. It's built for AI agents that read, summarize, or monitor web content, for enriching CRM, KYC, or fintech pipelines with company and brand data, and for extracting a competitor's design system or structured product and pricing data at scale.
Other clients
Apify works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Apify tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In your DSH project, or the patch file you mount plugins from.
One plugin instance is one MCP server. Add this to your plugin list.
Tools register as mcp__mewcp__<tool_name>. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
List all Actors in your Apify account. Returns basic information about each Actor including ID, name, and creation date.
Run an Actor on Apify platform. Provide Actor ID and input data. Returns run details including run ID and default dataset ID for results.
Get details of an Actor run including status, start time, finish time, and storage IDs.
List recent Actor runs from your account. Can filter by status.
Retrieve items from an Actor's default dataset. Results are the output data produced by the Actor run.
List Actor tasks in your account. Tasks are pre-configured Actor runs with saved input.
Check server readiness and basic connectivity.
