A client for the work between application code and the shell
Database investigations often start visually and end as code. You may need to find one document, compare environments, explain an index choice, or turn an exploratory filter into a repeatable maintenance script. MongoG keeps those steps in one desktop client instead of forcing every task into either a form-only GUI or a disconnected terminal session.
Connections, databases, collections, document results, and scripts share the same workspace. Open a collection to inspect records with bounded paging, then move to Query when the task needs a reusable filter, aggregation, bulk operation, or transaction. The selected connection and database stay visible so the script's execution context is clear.
Use the official driver model
MongoG query tabs provide real objects from the official MongoDB Node.js driver. The active db, collection helpers, BSON constructors, and cursor behavior follow the driver model rather than a proprietary query language. That makes examples easier to move between MongoG, application code, and official MongoDB documentation.
The editor provides typed method completions and sampled field suggestions. Schema-aware suggestions are guidance, not a database contract: a field absent from the sample may still exist, and one field can hold multiple BSON types. MongoG invalidates relevant schema cache entries after successful mutations so later suggestions can reflect changes.
Read script globals, BSON, and execution modes before running an unfamiliar maintenance script.
Control how scripts execute
Query Mode supplies the connected driver context while blocking unrelated process, module, timer, import, and network APIs. It is the default for normal database work. Trusted Script Mode exists for reviewed workflows that need explicitly permitted capabilities, but it should not be the default response to a script error.
Automatic await handles common driver promises without rewriting saved source. Sequential statements stay sequential; explicit Promise.all() communicates intentional parallel work. Selected-statement execution, cancellation, saved scripts, and history help developers return to an investigation without reconstructing every step.
Cancellation is cooperative across the desktop runtime and database driver. It cannot prove that the server stopped a write at the same instant, so important writes should remain idempotent and their final state should be verified.
Inspect results without losing BSON meaning
MongoDB returns more than ordinary JSON. MongoG preserves values such as ObjectId, Date, Decimal128, Int32, Long, Binary, and regular expressions. Document cursors are paged instead of being converted into an unbounded in-memory array. Scalar results, write acknowledgements, console output, and change streams use result views suited to their behavior.
For visual changes, the collection workspace supports deliberate single-document inserts, replacements, and deletes with concurrency and read-only safeguards. For multi-document work, use an explicit script and preview the filter before a mutation.
Include administration in the same workflow
MongoG provides views for indexes, explain plans, bounded global search, change streams, and GridFS. Use them to answer operational questions while retaining the current connection context. Index creation, document writes, and GridFS deletion remain real database mutations and should be reviewed accordingly.
The administration tools guide explains the limits of each view and when a query script is a better fit.
Run the client on your platform
Choose a macOS .dmg for Apple silicon or Intel, a Windows x64 .exe, or a Linux x64 .rpm. Visit the dedicated MongoDB GUI for Mac, Windows, or Linux page for package details. All downloads use a version-pinned release artifact and a short-lived delivery URL; permanent storage credentials are never exposed.