NinjaOne MCP
Let your coding agent query NinjaOne fleet reports and a local cache for cross-endpoint MSP questions without chaining many REST calls.
Overview
NinjaOne MCP is a MCP server for the Operate phase that exposes NinjaOne reports and a local fleet store to AI agents over stdio.
What is this MCP server?
- Exposes NinjaOne reporting surfaces to MCP-capable agents over stdio transport (v0.1.0).
- Maintains a local store so agents can answer fleet-wide questions a single API call cannot.
- OAuth2 client credentials via NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, and NINJAONE_OAUTH_SCOPE.
- Ships as an mcpb package from Servosity msp-skills with pinned fileSha256.
- Targets MSP and IT operators who already standardize on NinjaOne RMM.
- Server schema version 0.1.0 with stdio transport
- Three required secret environment variables for NinjaOne OAuth
- Published as registryType mcpb with pinned package fileSha256
Community signal: 1 GitHub stars.
What problem does it solve?
NinjaOne’s APIs and reports answer one question at a time, so agents waste turns stitching data when you need fleet-wide MSP answers.
Who is it for?
Indie consultants and micro-MSPs who already use NinjaOne and want agent-driven fleet Q&A without a custom integration project.
Skip if: Builders with no NinjaOne tenant, or teams that only need occasional single-device lookups in the web UI.
What do I get? / Deliverables
After you register OAuth credentials and the mcpb package, your agent can query consolidated NinjaOne report data and local fleet context in one conversation.
- Agent-callable access to NinjaOne report data via MCP tools
- Local store queries for fleet-wide questions beyond single API responses
- Documented OAuth environment variable configuration for the server
Recommended MCP Servers
Journey fit
How it compares
MCP bridge to NinjaOne RMM and a local fleet cache—not a standalone monitoring SaaS or generic agent skill.
Common Questions / FAQ
Who is NinjaOne MCP for?
It is for developers and MSP operators who manage endpoints in NinjaOne and want Claude Code, Cursor, or Codex to read reports and fleet-wide state through MCP.
When should I use NinjaOne MCP?
Use it during operate and support workflows when you need cross-report or fleet-level answers that would otherwise take multiple NinjaOne API calls or manual exports.
How do I add NinjaOne MCP to my agent?
Install the mcpb release, set NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, and NINJAONE_OAUTH_SCOPE, then register the stdio server in your agent’s MCP configuration.