NinjaOne MCP Server

NinjaOne MCP is an MCP integration. Every NinjaOne report, plus a local store that answers fleet-wide questions no single API call can.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/ninjaone-v0.1.16/ninjaone-mcp.mcpb, version 0.1.16. Its declared MCP transport is stdio.

The package declares NINJAONE_BASE_URL: Base URL for the NinjaOne API. Leave the prefilled default unless your account uses a different regional or self-hosted host.; NINJAONE_CLIENT_ID (required): Set the NINJAONE_CLIENT_ID credential for the NinjaOne MCP server.; NINJAONE_CLIENT_SECRET (required): Set the NINJAONE_CLIENT_SECRET credential for the NinjaOne MCP server.; NINJAONE_OAUTH_SCOPE (required): Set the NINJAONE_OAUTH_SCOPE credential for the NinjaOne MCP server.; NINJAONE_TOKEN_URL: Token endpoint the client-credentials exchange posts to. Leave the prefilled default unless your tenant uses a different token endpoint.; NINJAONE_NO_CONFIG_WRITE: Set to 1 to keep credentials off disk. The token cache becomes a no-op, so the connector mints a fresh token each run instead of writing one to config.toml. Leave blank for the default cached behaviour..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.16 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.