// the take
XMage is a Java client-server engine that implements Magic: The Gathering's full rules, covering over 32,000 cards for duels, multiplayer, draft and tournament play against humans or AI. It's for people who want to actually play rules-correct Magic for free, self-hosted or on community servers, not for anyone looking to build on top of a card game API.
Server-side rules enforcement means clients never see hidden information they shouldn't, so there's no client-side cheating vector by design. ~9000 unit tests at ~80% coverage is a real commitment for a project modeling thousands of card interactions, and a dedicated GitHub Action keeps card data synced from MTGJSON/Scryfall as new sets release. Format coverage is unusually deep: Commander, Oathbreaker, Cube, swiss/elimination tournaments, drafts with sideboarding, up to 10-player games.
The client is a Swing desktop app from the Java 8 era — the FAQ is full of GUI drawing artifacts, blank-screen freezes on startup, and M1/M2 Mac workarounds, which tells you how much platform-specific pain is baked in. The public server infrastructure is community-run and visibly fragile (the servers status page is itself marked 'temporarily out of service'), so uptime isn't something you can depend on if you're not self-hosting. Keeping a rules engine correct across 32,000+ cards and new sets every few months is a permanent, compounding maintenance cost that falls on volunteer maintainers, not a one-time build. There's no official public API or headless mode documented — it's built for its own client/server pair, not for integration into other tools.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →