Why would I compare these — they're so different?

Two reasons people end up googling this: (1) they want their AI agent to do what they used to do in Zapier, and they're trying to figure out if Zapier's new AI features replace MCP, or if they should use both; (2) they hear 'Zapier alternative' and assume it includes AI-agent infrastructure. wmcp.sh isn't a Zapier replacement — it's the agent-facing tool layer. If you have a Zapier Zap doing 'when Slack message, create Notion page', wmcp.sh doesn't replace that. But if you have an AI agent that needs to call Notion to create pages when asked, that's wmcp.sh's job.

When should I pick Zapier?

For traditional no-code workflow automation: triggers, multi-step Zaps, 6000+ apps, polished UX for non-technical users. Zapier is mature, reliable, and pays for itself fast in any team that needs cross-app automation without code. Their AI features are real but optional — the core product is workflows.

When should I pick wmcp.sh?

When you're building an AI agent — Claude.ai connector, Cursor MCP server, Codex tool — that needs to call external systems dynamically. wmcp.sh exposes any URL as MCP tools the agent can decide to call at runtime. Zapier's workflows are human-defined; wmcp.sh's tools are agent-discoverable.

Zapier has launched 'Zapier MCP' which exposes some Zapier actions as MCP tools — but it's a thin wrapper on their existing platform, scoped to apps they curate. wmcp.sh is MCP-native: every URL output is shaped for MCP from the start, with 5 oracle/price-data adapters and full OpenAPI ingest (Stripe, GitHub, Linear, etc.) that Zapier doesn't ship.

Zapier: free 100 tasks/mo, then $20+/mo for higher tiers. wmcp.sh: free 100 reads/day anonymous (3000/mo), $29/mo Pro for 10k/day. Different metering. Zapier's value is in the curated app library + UX; wmcp.sh's is in the MCP-native + OpenAPI breadth.

Yes. Zapier for traditional cross-app workflows your humans + business users build. wmcp.sh as the agent-facing tool layer for AI assistants. Many teams use Zapier to ingest events (e.g. Stripe → Slack notifications) AND wmcp.sh to expose data + actions to their AI agents.

head-to-head · honest framing

wmcp.sh vs Zapier.

Zapier is the no-code workflow incumbent — 6000+ apps, mature UX, the original "when X, do Y." wmcp.sh is the agent-facing tool layer — Claude / Cursor / Codex call MCP tools, not pre-defined Zaps. Different jobs, often complementary.

The shape difference

One sentence each.

Zapier

No-code workflow automation. Trigger + multi-step Zap. 6000+ apps. The incumbent for cross-app automation since 2011.

wmcp.sh

URL → MCP tools for AI agents. Agent picks which tool to call at runtime. Shopper-side + OpenAPI + oracle/DeFi adapters.

Side-by-side

The capability matrix.

Capability	Zapier	wmcp.sh
No-code workflow builder	✅ Industry standard	❌ Not the goal
SaaS app library	✅ 6000+ apps	⚠️ Anything with an OpenAPI spec, but no curated UX per app
AI agent tool_use shape Claude / OpenAI / MCP	⚠️ "Zapier MCP" wraps some actions; thin layer	✅ MCP-native from day 1
Shopper-side commerce	❌ Not in scope	✅ Shopify storefronts (4M+ stores)
Oracle / price-data	❌ Not in scope	✅ 5 adapters: CoinGecko, Pyth, Chainlink, DefiLlama, DexScreener
OAuth-proxy for MCP servers	❌ Not in scope	✅ RFC 7591 DCR + PKCE
Free tier	100 tasks/mo	100 reads/day anonymous (3000/mo)
Open source	❌ Closed	Worker + adapters MIT
Built for non-technical users	✅ Polished UX	❌ Developer + AI-builder audience

Where each wins

The honest version.

Zapier wins when:

You're a non-technical team automating cross-app workflows
You need 6000+ pre-built apps with hand-curated UX
Trigger-based automation is the job (not agent tool-use)
You want the most mature, reliable no-code workflow platform

wmcp.sh wins when:

You're building an AI agent that needs MCP tools (Claude.ai connector, Cursor, Codex)
You need MCP-native — Zapier MCP is a thin wrapper; wmcp.sh is built for it
You need shopper-side, oracle, or DeFi (Zapier doesn't ship these)
You want a 100/day anonymous free tier with no signup
You want OAuth-proxy for OAuth-gated MCP servers

Try wmcp.sh

One curl, no Zap builder.

curl 'https://wmcp.sh/api/v1/tools?url=https://api.llama.fi/protocols'
# 6 DeFi MCP tools, ready for Claude / Cursor / Codex.

FAQ

Common questions.

Why compare these — they're so different?

People ask if Zapier's AI features replace MCP, or if they should use both. wmcp.sh isn't a Zapier replacement. If you have a Zap doing "when Slack message, create Notion page", wmcp.sh doesn't replace that. wmcp.sh's job is the agent-facing tool layer.

When pick Zapier?

Traditional no-code workflow automation. 6000+ apps. Non-technical users.

When pick wmcp.sh?

AI agent building. MCP-native. Shopper-side + OpenAPI + oracle/DeFi.

Does Zapier do MCP?

Zapier launched "Zapier MCP" — a thin wrapper on their existing actions, scoped to curated apps. wmcp.sh is MCP-native from day 1, with 5 oracle adapters + full OpenAPI ingest Zapier doesn't ship.

Pricing?

Zapier: free 100 tasks/mo, $20+/mo higher tiers. wmcp.sh: free 100/day anonymous, $29/mo Pro.

Can I use both?

Yes — Zapier for cross-app workflows, wmcp.sh for AI agent tool layer. Common stack.