Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-apify scrape https://example.com to clean markdown"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Apify MCP — run web-scraping Actors and fetch their dataset results.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tool | Description |
| Run an Apify Actor (a cloud scraping/automation program) and get its dataset results in a single blocking call. The run is capped at 300 seconds. Pass the Actor input as an |
| Scrape a single web page (or crawl from it) and get clean, RAG-friendly markdown content. Convenience wrapper around the "apify~website-content-crawler" Actor. Example: apify_scrape_url({ url: "https://docs.apify.com/api/v2", _apiKey: "your-token" }). |
| Fetch items from an existing Apify dataset (e.g. the output of a prior Actor run). Example: apify_dataset_items({ datasetId: "abc123", limit: 50, _apiKey: "your-token" }). |
Related MCP server: Apify MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"apify": {
"url": "https://gateway.pipeworx.io/apify/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/apify/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1576+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"apify": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-apify"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-apifyIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Apify data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Run Signal Lab Apify Actors for price tracking, keywords, RAG, transcripts, Reddit, jobs, and menus.
YouTube transcripts, subtitles, and video metadata as structured JSON via an Apify Actor.
Apify MCP pinned to 30 Steadyfetch actors: ad, video and audio transcripts, trends, jobs, Amazon
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
