Ninjaone

io.github.LungshotPublished by GitHub account Lungshotv1.2.9Updated Oct 25, 2026

MCP server for NinjaONE RMM with device management, monitoring, and automation

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

A local MCP server for NinjaOne RMM that lets an assistant manage devices, monitor their status, and run automation tasks.

What you can do
Manage devices in a NinjaOne RMM environment through the assistant, including device-related operations and administration tasks. Monitor device and system status so the assistant can report on the managed fleet. Run automation actions against managed devices. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when you administer a NinjaOne RMM environment and want an assistant to look up devices, check their status, or trigger routine automation without switching to the NinjaOne console.
Requirements
Runs as a local process on the user's machine (stdio transport), desktop only. The manifest declares no package, so installation details are not documented. It presumably needs access to a NinjaOne RMM account or instance, but no credentials, environment variables, or headers are declared.
Before you install
It operates on a live RMM platform, so automation actions may change or act on managed devices; confirm what each action does before running it. Credentials for the NinjaOne account are not declared in the manifest, so check how the server obtains access before installing. No tool list is published, so the scope of what it can do is unverified.

Installation

In SourceWeft

  1. Open Ninjaone in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.9LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.