head-to-head · honest framing

wmcp.sh vs Composio.

Composio is the established player for owner-side SaaS connectors with managed OAuth. wmcp.sh is a different shape — shopper-side, OpenAPI ingest, MCP-native proxy, oracle/price-data adapters. Not a feature-by-feature dunk; here's when each one wins.

Both written by people on the wmcp.sh team. We tried to be fair. If Composio's team wants to publish a counter-page, we'll link to it.

The shape difference

One sentence each.

Composio

A platform for developers building owner-side AI apps to connect their customers' SaaS accounts (Slack / Notion / Linear / GitHub) via managed OAuth, with curated connectors and per-user token storage.

wmcp.sh

A worker that turns any public URL — Shopify storefronts, OpenAPI specs, oracle/price-data endpoints, OAuth-gated MCP servers — into MCP tools an agent can call. Shopper-side, broader, less curated.

Side-by-side

The capability matrix.

Capability Composio wmcp.sh
Owner-side SaaS connectors
user connects their own Slack / Notion / Linear		 ✅ Polished, curated, 100+ providers ⚠️ Available via OpenAPI ingest, but Composio's per-provider polish is real
Shopper-side commerce
agent buys from stores the user doesn't own		 ❌ Not in scope ✅ Shopify adapter on 4M+ public storefronts
OpenAPI spec ingest ⚠️ Some providers, hand-curated ✅ Any OpenAPI 3 spec URL → MCP tools automatically (Stripe ~400, GitHub ~900)
Oracle / price-data adapters
CoinGecko, Pyth, Chainlink, DefiLlama		 ❌ Not in scope ✅ 5 adapters live at /price-data
OAuth-proxy for MCP servers
e.g. DefiLlama MCP for Claude.ai users		 ⚠️ Different model (per-customer) ✅ wmcp.sh/mcp/<provider> proxies any RFC 7591 / PKCE MCP server
Free tier Limited free tier 100 reads/day anonymous, no signup
Pricing (developer tier) $39+/mo + usage $29/mo Pro
MCP-spec native ✅ MCP tool shape ✅ MCP tool shape + Streamable HTTP proxy + OAuth 2.1 DCR
Open source Partial (clients only) Worker + adapters public (MIT)
Multi-region / edge Centralized platform Cloudflare Workers, 300+ POPs
Managed agent-readiness consulting
we ship JSON-LD, OpenAPI, MCP server for your site		 ❌ Not offered ✅ From $499 one-time — see /managed
Where each wins

The honest version.

Composio wins when:

  • Your end-users have their own Slack/Notion/Linear and you need polished per-user OAuth that "just works" in production
  • You want hand-curated connectors that won't break when a vendor changes their API
  • Enterprise-grade SaaS tooling is the primary need; you're OK paying for the polish
  • You don't need shopper-side, oracle, or price-data surface

wmcp.sh wins when:

  • Your agent acts on systems the user doesn't own (shopper at Shopify stores, reader of DefiLlama, caller of public APIs)
  • You need OpenAPI ingest — Stripe's 400 endpoints or GitHub's 900 as MCP tools, no per-endpoint curation
  • You need oracle / DeFi / price-data (CoinGecko + Pyth + Chainlink + DefiLlama + DexScreener live)
  • You want OAuth-proxy for MCP servers (so Claude.ai / Cursor users get DefiLlama MCP without driving OAuth flows themselves)
  • You want a 100/day free tier with no signup
  • You want managed agent-readiness consulting (we ship the JSON-LD + MCP server for your site)
Try wmcp.sh in 30 seconds

One curl, see for yourself.

Drop any Shopify product URL, any OpenAPI spec URL, or any of the price-data sources. Free tier, no signup for the first 100 reads/day.

# Shopify product → 5 MCP tools (price, availability, add-to-cart, ...)
curl 'https://wmcp.sh/api/v1/tools?url=https://www.allbirds.com/products/mens-wool-runners'

# Stripe OpenAPI → 400+ MCP tools, with tag-filter:
curl 'https://wmcp.sh/api/v1/tools?url=https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json&tag=customers'

# DefiLlama → 6 MCP tools for TVL, yields, stables, ETFs
curl 'https://wmcp.sh/api/v1/tools?url=https://api.llama.fi/protocols'
FAQ

Common questions from people comparing these two.

What's the fundamental difference?
Composio is owner-side: it gives developers' customers OAuth-connected SaaS tools their agent can call on the customer's behalf. wmcp.sh is shopper-side + data-side: it exposes any public URL as MCP tools — Shopify storefronts, OpenAPI specs, oracle/price-data endpoints — without the user owning the upstream system. They overlap on a few SaaS providers but the wedges are different.
When should I pick Composio?
When you're building an owner-side SaaS app where your end users have their own Slack / Notion / Linear, you want polished per-customer OAuth UX, and you want curated managed connectors for the top 100 SaaS. Composio's curation is real.
When should I pick wmcp.sh?
When (a) your agent acts on systems your user doesn't own, (b) the upstream publishes an OpenAPI spec and you want every endpoint as MCP tools automatically, (c) you need oracle / price-data / DeFi adapters (Composio doesn't ship these), (d) you want a 100/day anonymous free tier, (e) you want MCP-native + OAuth-proxy for OAuth-gated MCP servers.
Can I use both?
Yes — most teams growing past a single product will. Composio for owner-side SaaS connectors that need polished OAuth. wmcp.sh for shopper-side, OpenAPI-ingested APIs, and oracle/price-data. Not zero-sum.
Pricing?
Composio: free tier (limited), then $39/mo per dev + usage. wmcp.sh: free 100 reads/day anonymous, $29/mo Pro for 10k/day reads + executes. Managed consulting from $499 one-time. wmcp.sh's free tier is materially larger for read-heavy workloads.
What about reliability?
Composio has had repeated platform outages reported in 2025-2026. wmcp.sh runs on Cloudflare Workers globally — every request hits the nearest edge, no central platform to fail. Different architectures, different failure modes.
Is wmcp.sh open source?
Worker + all 5 oracle adapters are MIT-licensed. Composio's clients are open, server is closed. If you need to self-host, wmcp.sh is the lower-friction path.