MyGamesAnywhere (MGA)
All your games. Your favorite launcher.
Your games are spread across stores, subscriptions, cloud folders and a NAS. MGA brings them into one private library, then shares that library with the launcher you already enjoy.
Run MGA on a Windows PC at home. Connect your sources, organize games and artwork, and give each person their own profile. Use Playnite or the LaunchBox preview plugin to browse and play. Manage the collection from a browser, including on your phone.
MGA is free, open-source and self-hosted. It is pre-1.0 software: expect rough edges and keep backups.
Get started — no developer tools needed
- Download the latest Windows release. Choose the file ending in
windows-amd64-installer.exe.
- Run setup. Choose For me only for a single PC, or All users for a household server on your trusted home network. The second option requires Windows administrator approval.
- Open MGA on this PC. Follow the first-profile setup, set your own password, and add a source under Sources.
- Install a frontend plugin and connect it to your MGA server and profile.
Full installation guide · Website · Release notes
You do not need a separate MGA Client. MGA manages and serves the library; your launcher handles playing, installation and emulators. If Windows warns about the unsigned installer, check the release's SHA256SUMS.txt before deciding whether to run it.
Why use MGA?
- Find the game, not the account. Bring supported stores and game folders into one collection, with separate profiles and source connections.
- Keep different copies straight. Track game versions, source locations and subscription availability without pretending every copy is interchangeable.
- Organize once. Manage descriptions, covers and other media centrally instead of repeating the work in each frontend.
- Keep your files at home. Serve authorized game files from your own sources to supported plugins. Store-owned games still use their store and account.
- Choose your launcher. Keep the frontend, emulator setup and controls you like. MGA is a source for it, not a replacement.
Frontend plugins
| Frontend | What is available |
|---|
| Playnite | MGA plugin 0.1.0: library import, metadata, artwork and authorized file downloads. Install from the plugin release; approval for the official add-on catalog is a separate step. |
| LaunchBox | Preview adapter: explicit library sync, metadata, artwork and authorized downloads. Not yet a public managed-plugin release or part of LaunchBox's native storefront scan. Big Box interaction is not separately validated. |
| Mobile | Browser-based management. There is no released mobile launcher plugin; do not expect the phone to play or install games through MGA. |
MGA 0.2.22 or newer is required for the plugins' profile-password sign-in. Check each plugin's own compatibility and download notes. These early adapters are not full game updaters: content-hash verification and cross-retry revision continuity are not complete. Do not use them to overwrite an existing installation after a source version changes.
Stores, folders and emulators
MGA has connectors for Steam, Xbox, Google Drive and SMB/NAS sources, plus experimental sources and metadata providers. Provider availability and sign-in requirements vary; see Works with MGA and the setup shown by your installed version.
A Steam or Xbox library entry is not a redistributable game download. Their clients, subscriptions, licenses and account rules still apply. MGA does not bypass account restrictions, DRM or simultaneous-play limits.
MGA can maintain emulator/runtime artifacts and serve them where licensing, provenance and integrity checks allow. You still configure and run emulators in your frontend. No games, ROMs, firmware or paid entitlements are bundled. Google Play catalog support does not imply an Android download, license transfer or working Google Play Games launcher integration.
For developers
The server is written in Go. Its profile-aware WebUI manages sources, games, catalog availability, emulator/runtime artifacts and frontend access. Scoped Frontend API clients consume metadata, media and authorized content; local execution belongs to the frontend.
To run a separate development server, install Go, Node.js and npm:
cd server/frontend
npm ci
npm run build
cd ..
go run ./cmd/server --runtime-mode user --app-dir "$PWD" --data-dir "$PWD/.dev-data" --no-tray
Open http://127.0.0.1:8900 and complete the first-profile setup. Use a separate data directory and do not start this alongside an existing server on the same port.
Verification:
cd server/frontend
npm run test:unit
npm run build
cd ..
go test ./...
go vet ./...
Contributors and agents: start with AGENTS.md, CLAUDE.md and docs/agent-bootstrap.md. Current product and operating guidance lives in the MGA Confluence space; Jira MGA is the source of truth for work state. Historical client/player code and dated documents are not current product guidance.
See VERSION and LICENSE.md.
