NinjaOne MCP

MCP server for NinjaOne (NinjaRMM) with hierarchical tool loading for managing devices, organizations, alerts, and tickets.

Installation

Run the MCP server with npx:

Or install the package:

MCPB Bundle (Claude Desktop)

Download the .mcpb bundle from GitHub Releases for a zero-config Claude Desktop install. No Node.js or terminal required — just open the bundle in Claude Desktop via Settings → MCP Servers → Install from file. Requires Claude Desktop 0.10+.

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "ninjaone": {
      "command": "npx",
      "args": [
        "@wyre-technology/ninjaone-mcp"
      ],
      "env": {
        "NINJAONE_CLIENT_ID": "your-ninjaone-client-id",
        "NINJAONE_CLIENT_SECRET": "your-ninjaone-client-secret"
      }
    }
  }
}

Authentication

Getting Credentials

Vendor portal: https://www.ninjaone.com/

Prerequisites

• NinjaOne account with Administrator role
• Knowledge of your NinjaOne deployment region (us | eu | oc — visible in your NinjaOne portal URL)
• Awareness that NinjaOne uses OAuth 2.0; you create an "API Application" record to issue tokens

Steps

1. Sign in to your NinjaOne console as an Administrator.
2. Navigate to Administration → Apps → API.
3. Click "Add" to create a new API Application.
4. Fill in:
   • Application Name: "WYRE Gateway"
   • Application Platform: API Services (machine-to-machine, NOT user-facing)
   • Redirect URI: not required for client_credentials grant
   • Scope: select scopes per least-privilege for the entities you need (monitoring, management, control)
5. Save the application. NinjaOne generates NINJAONE_CLIENT_ID and NINJAONE_CLIENT_SECRET.
   • Save NINJAONE_CLIENT_SECRET before leaving — NinjaOne only shows it once.
6. Set NINJAONE_REGION to your deployment region (us is default; eu / oc if applicable).

Required Scopes / Permissions

• monitoring (read endpoints, alerts)
• management (modify endpoints — devices, organizations)
• control (run actions on endpoints — reboots, scripts)
• Adjust per the tools you intend to use; least-privilege is recommended (start with monitoring only, add as needed)

Credential Format

Client ID is a UUID. Client Secret is a long random string. NINJAONE_REGION enum: us | eu | oc.

Rotation

Regenerate the client_secret from the same API Application page. Old secret remains valid until explicitly revoked; supports zero-downtime rotation.

Architecture

Hierarchical tool loading with navigation-based domain selection and lazy-loaded handlers.

Available Tools (21)

Tools are organized into 4 domains:

Devices

Manage endpoints, reboot devices, view services and alerts.

Organizations

Manage customer organizations and their resources.

Alerts

View and manage alerts across all devices.

Tickets

Manage service tickets.

Rate Limits

Varies by endpoint. The underlying client library handles rate limiting automatically.