Skip to content

Install the agent

The mngd agent is a small macOS app that reports installed software, scans for CVEs, and applies patches on a schedule. Installing it is the first step after signing up.

The agent pkg is universal — the same build works for every org. Org-specific configuration happens after install via an enrollment token you paste into the agent (or push via MDM config profile for multi-device deployments).

This is the right path for getting your first Mac enrolled, or for small shops without MDM.

  1. Get your enrollment token. In the mngd web app, go to Settings → Enrollment and click Generate new token. The plaintext token is shown exactly once — copy it now. It looks like mngd_K7X2-M9QR-4WPN.

  2. Download the pkg on the Mac you want to enroll:

    mngd-agent-latest.pkg

    The pkg is signed with our Developer ID and notarized by Apple. Gatekeeper will accept it on double-click.

  3. Install by double-clicking the downloaded pkg.

  4. Open mngd from your Applications folder. On first launch the agent prompts for an enrollment token — paste the token from step 1 and click Enroll.

  5. The agent checks in within 30 seconds. The device appears under Devices in the web app shortly after.

Option 2 — MDM deployment (multiple Macs)

Section titled “Option 2 — MDM deployment (multiple Macs)”

For deploying to many Macs at once through Jamf Pro, Iru, Intune, Addigy, or Mosyle.

  1. In the mngd web app, go to Settings → Enrollment, generate a token, and while the reveal banner is still up, click Profile next to the token to download a .mobileconfig file. The profile carries your enrollment token pre-configured.

  2. Upload the .mobileconfig to your MDM and deploy it to the target Macs.

  3. Upload the same mngd-agent-latest.pkg to your MDM and deploy via the MDM’s InstallApplication or Install Package flow.

  4. Devices enroll silently on first launch — no user interaction.

Step-by-step guides for the two most common MDMs:

  • macOS 14 (Sonoma) or later
  • Apple silicon or Intel
  • Network access to api.mngd.app and cdn.mngd.app

You don’t need to redeploy the pkg when a new agent version ships — the agent updates itself. See agent updates for how that works and how to publish a new version.

The agent handles software inventory, CVE scanning, and patching on its own. For the MDM side (configuration profiles, declarations, compliance), see enrollment — only required for mngd orgs; mngd patch is agent-only.