NinjaOne MCP server
MCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.
B70/100grade B
Adoption
Growing
26 stars
Reviews
Write oneNobody has reviewed NinjaOne yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
NinjaOne tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add ninjaone-mcp -- docker run -i --rm ghcr.io/wyre-ai/ninjaone-mcp:v2.3.1
NinjaOne: common questions
- Is NinjaOne MCP server safe?
- Mostly: it is graded B (70/100). Read the NinjaOne safety report
- How do I install NinjaOne?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does NinjaOne need an API key?
- Yes. The registry entry asks for
NINJAONE_CLIENT_SECRET. - Is NinjaOne maintained?
- The last commit was 4 days ago (2026-09-16). The latest release is v2.3.1.