Ninja MCP Server

What is Ninja MCP Server?

A PowerShell-based integration platform for the NinjaRMM (NinjaOne) API, designed for Managed Service Providers (MSPs) to automate device monitoring, report generation, and management tasks. It runs on Managed Cloud Provider (MCP) servers.

How to use Ninja MCP Server?

Clone the repository, configure API credentials in config.json, create required directories (reports, logs), then run example scripts like MCP-Tasks-Main.ps1 with parameters such as -ExportDeviceInventory, -GenerateAlertReport, -CheckDiskSpace, and -VerifyPatchStatus.

Key features of Ninja MCP Server

• Full NinjaRMM API integration via PowerShell module
• Automated device status and alert monitoring
• HTML report generation for device statistics
• Configurable email alerts for detected issues
• Extensible architecture for custom functionality
• Compatible with MCP server environments

Use cases of Ninja MCP Server

• Automate daily device health checks across multiple organizations
• Generate and distribute patch compliance reports
• Monitor disk space and alert on critical thresholds
• Export device inventory for asset management

FAQ from Ninja MCP Server

What dependencies does Ninja MCP Server require?

Windows Server 2016 or later, PowerShell 5.1 or later, and valid NinjaRMM API credentials (Client ID and Client Secret).

Where does Ninja MCP Server store generated data?

Reports are saved in the reports directory, logs in the logs directory, and configuration is stored in config/config.json.

How does authentication work?

The server uses a Client ID and Client Secret obtained from the NinjaRMM (NinjaOne) platform, along with a region parameter (e.g., "US") passed to each script.

What transports or protocols are used?

It communicates with the NinjaRMM REST API over HTTPS using PowerShell's Invoke-RestMethod.

Are there any known limitations?

No limitations are explicitly mentioned in the provided README.