A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 15.8 · decisive
A · leads
99.1
72,721 stars · MIT
B
83.3
4,841 stars · Apache-2.0
act 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. act is written mainly in Go; mcp-context-forge is written mainly in Python. The composite score is 99.1 for act and 83.3 for mcp-context-forge.
act has 72,721 GitHub stars to mcp-context-forge's 4,841, a gap of 67,880 (15.02×). Forks are 2,126 for act 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 90.
Push history: act was last pushed on 16 November 2026 (1 day ago), and mcp-context-forge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 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.
act 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 act and 96 for mcp-context-forge. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 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: act is open source, mcp-context-forge is open source.
act 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).
act finishes ahead at 99.1 against mcp-context-forge at 83.3, a 15.8 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 | act | mcp-context-forge |
|---|---|---|
| GitHub stars | 72,721 | 4,841 |
| Forks | 2,126 | 978 |
| Open issues | 318 | 987 |
| Adoption | 100 | 76 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 83.3 |
Run your GitHub Actions locally 🚀
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.
act has more GitHub stars: 72,721 versus 4,841 for mcp-context-forge. The gap is 67,880 stars.
mcp-context-forge was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.
Yes. This catalog marks both act and mcp-context-forge as self-hostable. Confirm each project's deploy docs before you plan a migration.
act 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.
act scores 99.1 and mcp-context-forge scores 83.3. This page calls that a decisive lead for act.