ninjaone

The NinjaOne MCP server provides a hierarchical, lazy-loading interface for interacting with NinjaOne APIs. It starts with a single navigation tool (ninjaone_navigate) and, based on your selections (devices, organizations, alerts, tickets), loads domain-specific tools on demand. This design keeps the initial surface area small and responsive, while still giving you access to a rich set of operations across devices, organizations, alerts, and tickets as you drill down. You can inspect device lists, get details, reboot devices, manage services, view alerts, and handle tickets through the corresponding domain tools, all orchestrated by the navigation and domain tools.

To use it, deploy the MCP server (via npm/npx as described in the installation section) and authenticate using the configured OAuth credentials (NINJAONE_CLIENT_ID and NINJAONE_CLIENT_SECRET). When you start a domain (for example devices or alerts), the server will expose the tools relevant to that domain, such as ninjaone_devices_list or ninjaone_alerts_summary. You can chain actions in a workflow like navigating to a domain, listing items, and then performing domain-specific operations, all while the server lazily loads the necessary client and handlers for that domain.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your machine
• Access to the internet to fetch the MCP package
• OAuth credentials from NinjaOne (NINJAONE_CLIENT_ID and NINJAONE_CLIENT_SECRET)

1. Install the MCP package globally (or use npx as shown in the README):

   npm install @wyre-technology/ninjaone-mcp

2. Set up environment variables for authentication (example for Unix-like shells):

   export NINJAONE_CLIENT_ID="your-client-id" export NINJAONE_CLIENT_SECRET="your-client-secret" export NINJAONE_REGION="us" # optional; defaults to us if not set

3. Run the MCP server using npx (as per the README):

   npx @wyre-technology/ninjaone-mcp

   Alternatively, integrate with Claude Desktop or a one-click deployment by using the provided configuration block in the README to point to this MCP server.

4. (Optional) Docker-based deployment:

   docker build -t ninjaone-mcp . docker run -e NINJAONE_CLIENT_ID=xxx -e NINJAONE_CLIENT_SECRET=xxx -e NINJAONE_REGION=us ninjaone-mcp

Notes and tips:

• The server loads domain handlers on demand to minimize startup time and reduce cognitive load. You’ll see domain-specific tools appear after you navigate to a domain.
• Ensure your OAuth credentials have the appropriate scopes for the actions you intend to perform (read/list vs. mutate actions like reboot or create tickets).
• If you change the region, update NINJAONE_REGION accordingly to point to the correct base URL (us, eu, oc).
• In Claude Desktop or other integrations, you can pass the environment variables to the MCP so that authentication succeeds without interactive prompts.
• If you run into rate limits or API errors, verify that your Client ID/Secret are valid, and consider adding retry logic or token refresh handling in your workflow.