Head to head
Contentrain vs alces-mcp
Same numbers we show everywhere else, lined up. Ratings come from users, the grade comes from our scanner, adoption comes from public registries.
No reviews yet
Git-native content governance for AI agents — 27 deterministic MCP tools over stdio and HTTP.
Full listing
No reviews yet
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
Full listingThe short version
Neither has been reviewed yet, so the comparison rests on the scan and the public usage numbers. The safety scan favours Contentrain (86/100 against 55). Contentrain is hosted and callable through the gateway; alces-mcp runs on your own machine. Contentrain has noticeably more public adoption.
| Contentrain | alces-mcp | |
|---|---|---|
| User rating | No reviews yet | No reviews yet |
| Safety grade | A86/100 | C55/100 |
| Adoption | Established | New |
| GitHub stars | 4 | – |
| Downloads / week | 1.5k | 403 |
| Runs where | Hosted (remote) | Your machine (local) |
| Gateway-ready | Yes | No |
| Tools | — | — |
| Write actions | — | — |
| Price per call | Free | Free |
| Licence | MIT | MIT |
| Last release | 2026-09-18 | — |
| Category | Developer tools | Developer tools |