Kongvsmetamcp
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Kong | metamcp | |
|---|---|---|
| Score | 81/100 | 60/100 |
| Rank in category | #1 of 18 in API Management | #15 of 38 in API Gateway |
| GitHub stars | 44 403 | 2 762 |
| Stars, last 30 days | +124 | +50 |
| Stable releases, 12 months | 4 | 2 |
| Latest release | 3.9.5 · 19 Nov 2026 | v2.4.22 · 19 Dec 2025 |
| Setup | Advanced | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Lua | Typescript |
Which one should you pick?
Kong scores 81/100 against 60/100 for metamcp, so it is the safer default.
Kong ships more often: 4 stable releases in the past year, against 2 for metamcp.
If you want the quickest setup, metamcp is easier to run; Kong needs more configuration.
Kong is growing faster right now (+124 stars in 30 days).
metamcp is archived, so it won't get fixes. Prefer the other one for anything long-lived.
Key differences
- License: Kong is Apache-2.0, metamcp is MIT.
- Language: Kong is written mainly in Lua, metamcp in Typescript.
- Features only Kong lists: AI Gateway, API Gateway, Authentication, Hybrid Mode and 4 more.
- Features only metamcp lists: API Key Authentication, MCP inspector, MCP Server Aggregation, MCP tools, resources and prompts and 10 more.
- Both offer: Rate Limiting.
Kong details →metamcp details →
Swap a project
Keep Kong, compare it with
Keep metamcp, compare it with