A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 14.5 · clear
A · leads
96.5
59,134 stars · MIT
B
82.0
4,841 stars · Apache-2.0
Gitea 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. Gitea is written mainly in Go; mcp-context-forge is written mainly in Python. The composite score is 96.5 for Gitea and 82.0 for mcp-context-forge.
Gitea has 59,134 GitHub stars to mcp-context-forge's 4,841, a gap of 54,293 (12.22×). Forks are 7,414 for Gitea and 978 for mcp-context-forge. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 77.
Push history: Gitea 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 2,172 for Gitea (0.037 per star) and 987 for mcp-context-forge (0.204 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
Gitea is listed as MIT, 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. License scores in this pair are 96 for Gitea and 96 for mcp-context-forge. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 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: Gitea is open source, mcp-context-forge is open source.
Gitea 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 36 points (70 vs 34), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against mcp-context-forge at 82.0, a 14.5 point clear 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 | Gitea | mcp-context-forge |
|---|---|---|
| GitHub stars | 59,134 | 4,841 |
| Forks | 7,414 | 978 |
| Open issues | 2,172 | 987 |
| Adoption | 100 | 77 |
| Activity | 100 | 100 |
| Community | 100 | 77 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 82.0 |
Gitea is a lightweight self-hosted Git service with issues, pull requests, and actions. It is the usual choice when a team wants a small forge they can run themselves.
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.
Gitea has more GitHub stars: 59,134 versus 4,841 for mcp-context-forge. The gap is 54,293 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and mcp-context-forge as self-hostable. Confirm each project's deploy docs before you plan a migration.
Gitea is listed as MIT, 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.
Gitea scores 96.5 and mcp-context-forge scores 82.0. This page calls that a clear lead for Gitea.