Apify vs zapier-webhooks
Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). zapier-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:42cc91f13363 Forks (GitHub): 368 Pulls (Docker Hub): 36 705 Stars (Docker Hub): 0 Stars (GitHub): 12 426 Not marked · First seen |
Not listed |
| Community marketplace hookdeck/webhook-skills | Not listed | Listed Version: not stated No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Apify | zapier-webhooks |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 426 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 36 705 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 368 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/apify-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/apify/actors-mcp-server | github.com/hookdeck/webhook-skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Apify
Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.
zapier-webhooks
Receive and authenticate webhooks sent by the Webhooks by Zapier action (POST, PUT, Custom Request). Use when building an endpoint that a Zap calls, when asking how to verify a Zapier webhook signature (there is none: add an X-Webhook-Secret header or Basic Auth in the Zap and compare constant-time), when parsing the user-defined Form, JSON, XML or Raw payload, or when a Zap's webhook step shows as errored. Also points to Standard Webhooks verification for Zapier white-label connection webhooks, which are a separate product.
How to run each
Apify As a local MCP server: Docker image
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio apify-mcp-server -- docker run -i --rm -e APIFY_TOKEN mcp/apify-mcp-server
Requires: APIFY_TOKEN (secret)
zapier-webhooks As a Claude Code plugin
/plugin marketplace add hookdeck/webhook-skills
/plugin install zapier-webhooks@webhook-skills
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of zapier-webhooks publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of zapier-webhooks publish no settings it asks for, so we do not compare settings.
What it can do: Apify · What it can do: zapier-webhooks · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.