HyperSwitchvsmetamcp
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| HyperSwitch | metamcp | |
|---|---|---|
| Score | 81/100 | 61/100 |
| Rank in category | #2 of 9 in Fintech | #10 of 39 in API Gateway |
| GitHub stars | 45 509 | 2 734 |
| Stars, last 30 days | +1 679 | +48 |
| Stable releases, 12 months | 2 | 3 |
| Latest release | v1.127.0 · 23 Sept 2026 | v2.4.22 · 19 Dec 2025 |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Rust | Typescript |
Which one should you pick?
HyperSwitch scores 81/100 against 61/100 for metamcp, so it is the safer default.
metamcp ships more often: 3 stable releases in the past year, against 2 for HyperSwitch.
If you want the quickest setup, metamcp is easier to run; HyperSwitch needs more configuration.
HyperSwitch is growing faster right now (+1 679 stars in 30 days).
HyperSwitch details →metamcp details →
Swap a project
Keep HyperSwitch, compare it with
Keep metamcp, compare it with