How to Uninstall Mockoon on Mac

Mockoon mock APIs are JSON data files, and the app can store settings and environments under its support folder. Locate each environment with its Show data file in Finder action and copy wanted files before uninstalling. The recorded test used a direct download, not a Homebrew installation.

Remove the app and inspect its data

Stop any running local mock servers, quit Mockoon and move Mockoon.app from Applications to Trash. Its CLI, if separately installed, is a different component. Vendor guidance describes per-environment files; settings documentation names ~/Library/Application Support/mockoon/storage. Do not assume a data file moved elsewhere is inside the app folder. Vendor guidance.

Check the result

ls -ld ~/Library/'Application Support'/mockoon ~/Library/Logs/Mockoon

Run this read-only check after quitting the app. A printed path still exists; “No such file or directory” means that path is absent, while a permission error needs its own investigation.

If you installed it with Homebrew

The Homebrew cask has a zap list that includes Application Support/mockoon, logs and preferences; the support folder can hold environment JSON. Run the command below without --zap if you want to keep those files and inspect them separately. A manual --zap follows the whole cask list regardless of Mole’s checkboxes. Mole uses zap only when its targets are selected, owned and within the checked boundary; otherwise it removes selected remnants through its own flow.

brew uninstall --cask mockoon

What Mole lists

The lower-case display-name Application Support/mockoon is a review row, unselected by default. Exact bundle-ID preferences are normally selected; environment files outside Library are not gathered by this rule.

What this test covered

The official Mockoon 9.9.0 app was copied and removed on September 20, 2026. No mock API was created or run, and no cloud environment or CLI was tested.