A · leads
Coolify
99.1
66,171 stars · Apache-2.0
DevOps
Coolify leads by 17.1 · decisive
A · leads
99.1
66,171 stars · Apache-2.0
B
82.0
4,841 stars · Apache-2.0
Coolify versus mcp-context-forge is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Coolify is written mainly in PHP; mcp-context-forge is written mainly in Python. The composite score is 99.1 for Coolify and 82.0 for mcp-context-forge.
Coolify has 66,171 GitHub stars to mcp-context-forge's 4,841, a gap of 61,330 (13.67×). Forks are 6,003 for Coolify and 978 for mcp-context-forge. On the log scale used inside this pair, adoption is 100 versus 76, and the fork community is 100 versus 79.
Push history: Coolify was last pushed on 17 November 2026 (0 days ago), and mcp-context-forge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 149 for Coolify (0.002 per star) and 987 for mcp-context-forge (0.204 per star). Issue-health scores are 96 and 34; activity scores are 100 and 100.
Both Coolify and mcp-context-forge are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Coolify (66,171 stars) and mcp-context-forge (4,841 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Coolify is open source, mcp-context-forge is open source.
Coolify is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 62 points (96 vs 34), and the tightest is self-hosting at 0 points (100 vs 100).
Coolify finishes ahead at 99.1 against mcp-context-forge at 82.0, a 17.1 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Coolify | mcp-context-forge |
|---|---|---|
| GitHub stars | 66,171 | 4,841 |
| Forks | 6,003 | 978 |
| Open issues | 149 | 987 |
| Adoption | 100 | 76 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 82.0 |
Coolify is a self-hosted application platform in the Heroku mold. It deploys apps, databases, and prebuilt services onto servers you control.
An AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.
Coolify has more GitHub stars: 66,171 versus 4,841 for mcp-context-forge. The gap is 61,330 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Coolify and mcp-context-forge as self-hostable. Confirm each project's deploy docs before you plan a migration.
Coolify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. mcp-context-forge is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Coolify scores 99.1 and mcp-context-forge scores 82.0. This page calls that a decisive lead for Coolify.