A · leads
Grafana
91.2
77,962 stars · AGPL-3.0
DevOps
Grafana leads by 10.7 · clear
A · leads
91.2
77,962 stars · AGPL-3.0
B
80.5
4,841 stars · Apache-2.0
Grafana 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. Grafana is written mainly in TypeScript; mcp-context-forge is written mainly in Python. The composite score is 91.2 for Grafana and 80.5 for mcp-context-forge.
Grafana has 77,962 GitHub stars to mcp-context-forge's 4,841, a gap of 73,121 (16.10×). Forks are 14,988 for Grafana and 978 for mcp-context-forge. On the log scale used inside this pair, adoption is 100 versus 75, and the fork community is 100 versus 72.
Push history: Grafana 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 3,310 for Grafana (0.042 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.
Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for Grafana and 96 for mcp-context-forge. This is a procurement signal, not legal advice.
In DevOps, both Grafana (77,962 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: Grafana is freemium, mcp-context-forge is open source.
The lead is split. Grafana is furthest ahead on issue health (70 to 34), while mcp-context-forge is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Grafana finishes ahead at 91.2 against mcp-context-forge at 80.5, a 10.7 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 | Grafana | mcp-context-forge |
|---|---|---|
| GitHub stars | 77,962 | 4,841 |
| Forks | 14,988 | 978 |
| Open issues | 3,310 | 987 |
| Adoption | 100 | 75 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 34 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 80.5 |
Grafana is the dashboard and visualization layer most teams pair with Prometheus and other metric stores. The open-source server can be self-hosted; Grafana Labs sells a cloud.
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.
Grafana has more GitHub stars: 77,962 versus 4,841 for mcp-context-forge. The gap is 73,121 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Grafana and mcp-context-forge as self-hostable. Confirm each project's deploy docs before you plan a migration.
Grafana is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
Grafana scores 91.2 and mcp-context-forge scores 80.5. This page calls that a clear lead for Grafana.