krakendvsmcp-gateway
Two self-hosted API Gateway projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| krakend | mcp-gateway | |
|---|---|---|
| Score | 63/100 | 41/100 |
| Rank in category | #10 of 38 in API Gateway | #27 of 38 in API Gateway |
| GitHub stars | 2 704 | 26 |
| Stars, last 30 days | +13 | +0 |
| Stable releases, 12 months | 18 | 23 |
| Latest release | v3.0.4 · 12 Nov 2026 | gateway-v1.0.2 · 1 Nov 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Rust |
Which one should you pick?
krakend scores 63/100 against 41/100 for mcp-gateway, so it is the safer default.
mcp-gateway ships more often: 23 stable releases in the past year, against 18 for krakend.
If you want the quickest setup, krakend is easier to run; mcp-gateway needs more configuration.
krakend is growing faster right now (+13 stars in 30 days).
Key differences
- License: krakend is Apache-2.0, mcp-gateway is MIT.
- Language: krakend is written mainly in Go, mcp-gateway in Rust.
- Platforms only krakend lists: AWS, Debian, Docker, Homebrew.
- Platforms only mcp-gateway lists: Helm.
- Features only krakend lists: API aggregation and composition, Automatic content encoding conversion, Backend response caching, Circuit Breaker and 10 more.
- Features only mcp-gateway lists: Adapter for stdio MCP servers, Admin CLI, API Key Authentication, Audit Logging and 9 more.
krakend details →mcp-gateway details →All API Gateway projects →