How to uninstall NoSQLBooster on Mac
Save connection settings, scripts and exported files before removing NoSQLBooster for MongoDB. This guide covers the official Mac app, with a separate Homebrew section. Removing a database client does not call for dropping collections, deleting a MongoDB server’s data or removing MongoDB Compass.
Back up client data before quitting
NoSQLBooster supports connection backups and importing connection JSON or URI lists, described in its official connection-backup notes. Use the connection backup/export controls in your installed app and save the resulting file outside the folders you plan to remove. Connection backups may contain private access details; do not share them publicly.
Save open scripts and wanted query exports. Then quit NoSQLBooster with Cmd + Q, and copy ~/Library/Application Support/NoSQLBooster for MongoDB to a separate backup location using Finder. This support directory was created in our local test. A copy of client settings is not a database backup; arrange server backups separately if you need them.
Remove the app and review its folders
Move NoSQLBooster for MongoDB.app from Applications to the Trash after quitting it. To inspect the remaining locations, use Finder › Go › Go to Folder:
| Location | What to do |
|---|---|
~/Library/Application Support/NoSQLBooster for MongoDB |
Keep for a reinstall or until connection and workspace data have been backed up. |
~/Documents/NoSQLBooster |
Inspect and save wanted documents first. This is a cask removal target, not a directory created in our test. |
~/Library/Preferences/com.nosqlbooster.mongodb.plist |
Keep for a troubleshooting reinstall, or remove to reset preferences. |
~/Library/Saved Application State/com.nosqlbooster.mongodb.savedState |
Saved window state, not server databases. |
~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/com.nosqlbooster.mongodb.sfl* |
Recent-document records belonging to this client, separate from the saved files. |
The extra locations come from the Homebrew cask. After checking the separate backups, move only confirmed unwanted NoSQLBooster items to the Trash. For sfl*, open the parent folder in Finder and select only existing filenames beginning with com.nosqlbooster.mongodb.sfl; * is a filename pattern, not a literal path. Keep the parent and other apps' records. A missing path needs no action. Leave MongoDB server data, Compass’s data and scripts stored elsewhere alone. App removal also does not cancel a purchased service or change your database account.
If you installed it with Homebrew
Uninstall without zap:
brew uninstall --cask nosqlbooster-for-mongodb
Direct --zap also targets the Documents folder above, app support, preferences, saved state and recent-document records, ignoring Mole’s selections. Back up first. Mole uses zap only when the complete scope passes review; unchecked, shared or unsupported targets suppress it, while selected remnants use Mole’s own removal path.
Check the result
These read-only checks assume the app was in Applications:
ls -d '/Applications/NoSQLBooster for MongoDB.app'
pgrep -ifl '/NoSQLBooster for MongoDB\.app/Contents/'
ls -d "$HOME/Library/Application Support/NoSQLBooster for MongoDB" "$HOME/Documents/NoSQLBooster"
An absent-app error confirms only that app path is gone. No pgrep output means no matching client process was found. A listed data folder is expected if you kept it; inspect your backup before deciding to remove it. Permissions errors leave a check unresolved. These checks do not connect to a server or prove a server database is healthy.
What Mole lists
The app support directory is listed but initially unselected when the app-data preference is off; opting in can select eligible reviewed data. The bundle-ID preferences are selected by default. Check both before removal if retaining settings. Do not assume the Homebrew Documents target is a selected Mole row merely because it appears in the cask.
What this test covered
On September 21, 2026, NoSQLBooster 11.1.6 from the official Mac package was copied into Applications, launched without connecting to a database, and removed with Mole. The approximately 2 MB app support directory was explicitly selected, and the app, that directory, preferences and temporary files were removed. Signed-in state, real connection recovery, database contents and Homebrew removal were not tested.