mcp-ninjaone

A Model Context Protocol (MCP) server for NinjaOne (formerly NinjaRMM), providing AI assistants with full access to remote monitoring and management through the NinjaOne REST API v2.

Features

19 tools across five categories:

Device Management

Organizations

Alerts & Conditions

Maintenance Windows

Jobs & Automation

Installation

git clone git@github.com:fredriksknese/mcp-ninjaone.git
cd mcp-ninjaone
npm install
npm run build

Configuration

The server is configured via environment variables:

Instance Hostnames

Creating API Credentials

1. Log in to your NinjaOne instance
2. Navigate to Administration > Apps > API
3. Click Add to create a new API application
4. Select Client Credentials as the authorization flow
5. Grant the required scopes: monitoring, management, control, offline_access
6. Copy the Client ID and Client Secret

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "ninjaone": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-ninjaone/dist/index.js"],
      "env": {
        "NINJAONE_CLIENT_ID": "your-client-id",
        "NINJAONE_CLIENT_SECRET": "your-client-secret",
        "NINJAONE_INSTANCE": "app.ninjarmm.com"
      }
    }
  }
}

Usage with Claude Code

Add to your Claude Code MCP settings:

claude mcp add ninjaone -- node /absolute/path/to/mcp-ninjaone/dist/index.js

Set the required environment variables before running, or configure them in your MCP settings.

Example Prompts

Once connected, you can ask your AI assistant things like:

• "Show me all devices that are currently offline"
• "What active alerts do we have across all organizations?"
• "Put device 1234 into maintenance mode for the next 2 hours"
• "List all devices for the Acme Corp organization"
• "What software is installed on device 5678?"
• "Show me recent activity for device 1234"
• "Run the cleanup script on device 9012"
• "What jobs are currently running across all devices?"
• "Reset all minor alerts for device 1234"
• "What patches are pending on device 5678?"

Development

npm run dev      # Run with tsx (auto-reloads)
npm run build    # Compile TypeScript to dist/
npm start        # Run compiled output

Architecture

src/
├── index.ts                # Entry point — creates MCP server + STDIO transport
├── ninjaone-client.ts      # HTTP client with OAuth2 client credentials flow
└── tools/
    ├── devices.ts          # Device management and inventory (7 tools)
    ├── organizations.ts    # Organization/client management (5 tools)
    ├── alerts.ts           # Alert monitoring and acknowledgement (4 tools)
    ├── maintenance.ts      # Maintenance window management (3 tools)
    └── jobs.ts             # Job execution and monitoring (3 tools)

The client handles OAuth2 token lifecycle automatically — tokens are fetched on first use and refreshed when they expire (typically after 1 hour).

Requirements

• Node.js 18+
• NinjaOne account with API access enabled

License

SEE LICENSE IN LICENSE