What's the difference between wmcp.sh and Smithery?

Smithery is a local CLI and hub that lets you install and run Model Context Protocol (MCP) servers locally inside Docker containers. wmcp.sh is a hosted edge gateway proxy that dynamically maps public APIs and storefronts to MCP tools, resolving requests at the edge with built-in out-of-band token vaulting.

When should I pick Smithery?

Choose Smithery when you are building local workflows on a single developer laptop and want to run existing open-source MCP servers securely in isolated Docker environments locally.

When should I pick wmcp.sh?

Pick wmcp.sh when building multi-user SaaS web applications, or when you require dynamic, zero-codegen OpenAPI spec resolutions, secure token isolation proxies, or shopper-side storefront integrations at the edge.

head-to-head · honest comparison

wmcp.sh vs Smithery.

Smithery is a local MCP server installer using Docker. wmcp.sh is a stateless, edge-hosted gateway and out-of-band proxy vault. Different shapes; here's the honest comparison.

The core difference

One sentence each.

Smithery

A local CLI tool and registry that compiles and runs existing open-source MCP integration servers locally inside containerized Docker environments.

wmcp.sh

A hosted, stateless edge gateway that maps public APIs and storefront catalogs to standardized MCP tools dynamically with out-of-band PKCE proxying.

Side-by-side

The capability matrix.

Capability	Smithery	wmcp.sh
Local Subprocess Installation	✅ Core feature, highly mature	❌ Out of scope — wmcp.sh runs on edge CDNs
Multi-Tenant SaaS Apps	❌ Not supported (Docker per user is heavy)	✅ Highly scalable, stateless edge gateway
Out-of-band Key Vaulting	❌ Not supported (local configs in plain-text)	✅ Built-in PKCE token isolation proxy
Dynamic OpenAPI Mapping	❌ Must write curated servers	✅ Dynamic OpenAPI specs compiled at runtime
Shopper-Side Commerce	❌ Not supported	✅ Shopify storefront tools out-of-the-box
Cold-start cost	⚠️ Docker pull + container boot on first launch (2–30s, then warm)	✅ No container — sub-50ms edge execution from first call

Where each wins

Honest evaluation.

Smithery wins when:

You want to run existing open-source MCP servers locally
You are building personal workflows on a single developer laptop
You prefer isolating servers inside local Docker containers

wmcp.sh wins when:

You are building multi-user SaaS web applications in the cloud
You require dynamic, zero-codegen OpenAPI-to-MCP edge translation
You require secure credentials vaulting out-of-band

Try wmcp.sh

One curl.

curl 'https://wmcp.sh/api/v1/tools?url=https://api.llama.fi/protocols'
# Dynamic tools resolved instantly at edge POPs, no Docker installs.

FAQ

Common questions.

What's the difference?

Smithery installs and runs MCP servers locally inside Docker containers. wmcp.sh translates public APIs and storefronts to standard tool schemas dynamically at the edge.

When pick Smithery?

Local single-dev laptop configurations and Docker-based setups.

When pick wmcp.sh?

Cloud-hosted SaaS agents, dynamic OpenAPI specs, secure PKCE vault proxying, and high-speed edge resolution.