Side-by-side MCP server comparison
Short answer: pick io.github.firebase/firebase-mcp. It scores 94/100 to io.github.patrickchugh/terravision's 89/100, and it is published by the vendor behind the API rather than by a third party, and it has 4,477 GitHub stars against 1,660. io.github.patrickchugh/terravision is still worth a look if you are already invested in it - the full breakdown below shows exactly where the 5 points go.
Last updated
| Metric | io.github.firebase/firebase-mcp | io.github.patrickchugh/terravision |
|---|---|---|
| MCPpedia Score | 94 | 89 |
| Security Score | 30 | 30 |
| Maintenance Score | 19 | 14 |
| GitHub Stars | 4.5k | 1.7k |
| Weekly Downloads | 2048.9k | 0 |
| Tools | 3 | 9 |
| Est. Token Cost | 450 | 1.4k |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | Yes | No |
| Transport | stdio, sse, http | http |
| License | MIT | AGPL-3.0 |
| API Pricing | freemium | freemium |
io.github.firebase/firebase-mcp leads with a score of 94 (A), ahead of io.github.patrickchugh/terravision's 89 (A).
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c