Skip to main content

Set up the NinjaOne MCP server

The NinjaOne MCP server gives AI agents access to your NinjaOne RMM environment for device monitoring, patch management, maintenance scheduling, and remote device actions. This guide covers registering an API app in NinjaOne, selecting the authorization method for your region, and connecting the server to MintMCP.

Prerequisites​

  • A MintMCP admin account
  • A NinjaOne administrator account (API app registration requires access to the Administration area in NinjaOne)

Create a NinjaOne API app​

NinjaOne requires a Web application registered in its API settings to broker OAuth sign-in for each user. A NinjaOne administrator must complete this step. For NinjaOne's own reference, see Create a regular web app.

  1. In NinjaOne, go to Administration > Apps > API.

  2. Click Client App IDs, then click Add.

  3. Set Application Platform to Web (PHP, Java, .Net Core, etc).

  4. Enter a Name for the app (for example, MintMCP).

  5. Under Redirect URIs, enter MintMCP's callback URL:

    https://app.mintmcp.com/oauth/callback

  6. Under Scopes, select Monitoring, Management, and Control:

    CapabilityNinjaOne scope
    Read device and organization dataMonitoring
    Modify devices, organizations, and run scriptsManagement
    Remote device access via APIControl

  7. Under Allowed Grant Types, select Authorization Code and Refresh Token.

  8. Click Save.

  9. Copy the Client ID and Client Secret. The Client Secret is displayed once; store it securely. If you lose it, open the app in NinjaOne under Administration > Apps > API > Client App IDs and regenerate the secret.

Add NinjaOne to MintMCP​

NinjaOne has five regional instances with separate OAuth endpoints. The authorization method you select in MintMCP must match the region your organization uses; a token issued for one region will not authenticate against another.

  1. In MintMCP, go to MCP store > Manage store > Recommended servers.

  2. Find the NinjaOne connector and click to install it.

  3. Select the authorization method that corresponds to your NinjaOne region. Your region is the domain you log into NinjaOne with:

    If you log in at...Select
    app.ninjarmm.comUS
    us2.ninjarmm.comUS2
    eu.ninjarmm.comEU
    ca.ninjarmm.comCanada
    oc.ninjarmm.comOceania

  4. Enter the Client ID and Client Secret from the app you registered.

  5. Confirm the Redirect URL shown in the install drawer matches the URI you entered in NinjaOne (https://app.mintmcp.com/oauth/callback). If they differ, update the redirect URI in the NinjaOne app before continuing.

  6. Click Install.

Security considerations​

  • The Management scope grants write access to device and organization data, including creating organizations, adding devices, and running scripts on managed endpoints.
  • Some tools trigger actions on managed devices and display confirmation warnings before executing. Review which tools are available to agents in MintMCP's tool customization settings.
  • Each user authenticates with their own NinjaOne credentials, so device actions are attributed to that user's account and governed by their NinjaOne permissions.
  • Keep the Client Secret out of source control. If it's exposed, regenerate it in NinjaOne under Administration > Apps > API > Client App IDs, then update it in MintMCP.
  • API app registration requires a NinjaOne administrator account. Check NinjaOne's API documentation to confirm API access is included in your plan.

Troubleshooting​

  • Sign-in fails after selecting a region. Confirm the authorization method in MintMCP matches your NinjaOne login URL. Tokens issued for one region do not work in another; if you switch the auth method, users must sign in again.
  • No Client Secret visible after saving the app. Only the Web platform generates a client secret. Confirm Application Platform is set to Web (PHP, Java, .Net Core, etc) and save the app again.
  • Redirect URI mismatch. The URI in NinjaOne does not match MintMCP's callback URL. Open the app under Administration > Apps > API > Client App IDs, update the redirect URI to https://app.mintmcp.com/oauth/callback, and save.
  • Questions about NinjaOne app registration. See NinjaOne's API OAuth documentation or contact NinjaOne support.

Next steps​