Gloss Mod Manager: a Chinese mod manager built on Tauri with an AI MCP layer

One entry point for browsing, downloading and removing mods

Gloss Mod Manager, abbreviated GMM, is described as a comprehensive smart game mod manager. The stated goal is to give players a simple, usable platform for downloading, installing and uninstalling mods, whether they are new to mod management or already have their own habits, and to gather the common flows behind a single entry point. The feature list is where the shape of the tool becomes clear. There is simple installation and downloading, convenient browsing and downloading of mods, custom tag categories, backup of saves and game files, a quick switcher for a library of games, automatic language adaptation to the system language, automatic adaptation of the theme to the system theme, automatic update checks, automatic handling of mod conflicts, and a user sorting system with a custom sort order. It runs on Windows, macOS and Linux, and the README also advertises a clean interface with no clutter, no bundled advertising, and every function free. The audience is a player rather than a mod author, with the exception of the mod package creation and upload features.

v2 cut the installer by 90 percent and added MCP and Skills

The v1 to v2 section is the most informative part of the README, because it names the two changes that matter. The first is size. The v2 version is a comprehensive upgrade of v1, and the most visible improvement is that the installer size dropped by 90 percent. The second is the AI layer. Version 2 introduced MCP and Skills tooling, which lets GMM use a large language model to manage mod packages and game files more intelligently. The compatibility claim is broad: in theory v2 is compatible with everything in v1, including the mod list, the game list, custom games, tag categories and backups, and the author asks to be told through GitHub if an upgrade goes wrong. That phrase, in theory, is doing some work in the README. It suggests migration was tested in one direction, and the README does not describe a rollback path or a migration tool, so a user with a large existing library has no documented way back other than reinstalling v1.

A Tauri shell around a Vue 3 and TypeScript interface

The repository layout tells you the stack. There is a src directory for the frontend, a src-tauri directory for the Rust side of Tauri, a components.json file for the component library, vite.config.ts, vitest.config.ts, a scripts directory, docs, and separate tsconfig files for the app, the node tooling and the scripts. The package.json is private with version 2.3.1 and the license LGPL-3.0-or-later, and the scripts show how the pieces are wired together:

        "dev": "vite",
        "build": "vue-tsc --noEmit && vite build",
        "test": "vitest run --config vitest.config.ts",
        "tauri": "tauri"

There are also lifecycle hooks that matter for anyone building it. The postinstall script runs prepare:sidecars, and the predev, prebuild and pretauri hooks run sync:version and prepare:sidecars, the latter of which prepares the native sidecar binaries the Tauri shell launches. The dependency list shows the Tauri 2 plugin set the application leans on, including autostart, cli, clipboard-manager, deep-link, dialog, fs, http, log, notification, opener, os, positioner, shell and store, and the AI side uses the AI SDK packages for MCP, an OpenAI compatible provider and Vue integration, alongside Vue 3, Tailwind 4, TanStack Table for the mod lists, Pinia, Drizzle ORM, better-sqlite3, and Three.js with React Three Fiber for the 3D previews.

API keys and Firebase configuration live in .env

The environment template shows what the application talks to. Four keys cover the mod sources, and then there is a Firebase block for the rest:

GLOSS_MOD_KEY=""
MODID_KEY=""
MODID_UID_KEY=""
CURSE_FORGE_KEY=""

The Firebase variables are VITE prefixed, which marks them as client-visible in a Vite build, and they cover the API key, auth domain, project id, storage bucket, messaging sender id, app id and measurement id. That last one is worth pausing on. The project also says it is safe, with no bundling, and that every function is free and open, and a Firebase measurement id implies analytics collection, which sits oddly next to a claim of no tracking. The README does not explain the Firebase usage, so whether it is analytics, crash reporting or something else is not documented, and a user who cares about that should ask the maintainer rather than infer. The Curse Forge key also suggests the application can pull from a commercial mod repository, which raises the question of what a Curse Forge account key does in a client-side bundle.

Two licences, and the question of what is actually in the repository

The licensing needs attention because the two sources disagree in a way that matters. The repository metadata reports the project as GPL-3.0, with a LICENSE file at the root. The package.json, which describes the application code itself, declares LGPL-3.0-or-later, and the package is marked private, so it is not published to a registry. That combination is workable, since LGPL-3.0 is compatible with GPL-3.0 distribution, but it is not the same as a clean single-licence project, and a reader who takes the package.json at face value would draw a different conclusion from the badge at the top of the README. The top-level entries also include a Privacy Policy.md, an AGENTS.md, a CLAUDE.md, a CodeStyle.md, a contribute.md and a CHANGELOG.md, which is the file set of a project that intends outside contributions, and the README says to contact the maintainer on Discord for help with development. The last push was on 2026-10-19 and the default branch is v2, so the v2 line is where the work is happening.

A roadmap written as a finished checklist

The development plan in the README is unusual, because every item is ticked. The list covers the overall tool style and interface, the base architecture and the mod browsing feature, downloading mods, installing and managing mods, adapting to popular games, automatic update checks, creating mod packages, user login, launching the game with a user-chosen game path, multi-language internationalisation with a language switcher, uploading mod packages to the mod site, adaptive system language, adaptive system theme, automatic mod update checks, a mod sorting feature with custom sort orders, and automatic handling of mod conflicts. Two of those carry caveats. The mod package creation feature is ticked but annotated as still needing refinement, and the user login feature is ticked with a note that it covers scanning login through the app and username and password login. The reason this list reads like a plan rather than a history is that this README documents a version that is close to feature-complete for its stated scope. The release history backs that reading: v2.2.0 on 2026-07-09, v2.3.0 on 2026-08-29 and v2.3.1 on 2026-08-31, with the pushes after that continuing into October.

Where the users are, and what is not documented

The distribution channels and the support channels are both listed, and they tell you what kind of project this is. Builds are available from a 3DM mod site listing, from GitHub releases, from the Microsoft Apps store, and from a network disk mirror, with a user guide hosted at gmm.aoe.top, a requirements page for mod prerequisites, a discussion thread for requesting new games, a questionnaire, and a sponsorship link. Feedback goes to GitHub Issues, a QQ channel, and a QQ group with the number 2169033132, and the development collaboration happens on Discord. The supported games list lives on its own page at the site. What the README does not document is just as telling. There is no build-from-source section for developers, no explanation of the MCP and Skills integration beyond the one sentence describing it, no description of what the Curse Forge key is used for, and no account or telemetry policy beyond the one-line claim of being free and unbundled. For a desktop application that installs files into your games and runs a language model against your library, those are the gaps a careful adopter will want closed, and the Discord channel and the GitHub issue tracker are where to ask.

Editorial conclusion

Gloss Mod Manager fits a player on Windows, macOS or Linux who wants one entry point for browsing, downloading, installing and removing mods, with save and game file backups and automatic conflict handling, and who is comfortable with a Chinese-first interface and a project run by one maintainer. It does not fit someone who needs the mod list synchronised across several machines, or who wants a guaranteed update path, since the roadmap is a flat checklist and the feedback channel is a chat group. Before installing, check the licence discrepancy between the repository and package.json, confirm the game you play appears in the supported list, and read the supported-games page rather than assuming a title is covered.

Frequently asked questions

Official sources

1. GlossMod/Gloss-Mod-Manager on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases