Ninja One MCP Server

A Model Context Protocol (MCP) server for interacting with NinjaOne, featuring a decision tree architecture for efficient tool loading.

People who need DevOps & monitoring tools inside Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-24 · ★ 23 · #83 OF 101 MAINTAINED DEVOPS & MONITORING · VERIFIED 2026-08-25

Apache-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Ninja One

before you install - you'll need

Set NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, NODE_AUTH_TOKEN before connecting. NINJAONE_REGION, NINJAONE_SCOPES are optional or environment-specific per the README.

Docker

docker run -i --rm ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9

Claude Desktop - add to config

{
  "mcpServers": {
    "wyre-technology-ninjaone-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9"
      ]
    }
  }
}
Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as container (OCI image) - can be sandboxed away from your filesystem

license Apache-2.0 - declared in the repository

registry namespace io.github.wyre-technology is GitHub-verified and matches the repo owner

03 · What Ninja One can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v2.2.9 · 2026-08-21

2.2.9 (2026-08-21) · preflight token check at startup, fix IPv4-only healthcheck (#88) (0deeab1), closes #87

v2.2.8 · 2026-08-20

2.2.8 (2026-08-20) · restore ninjaone-mcp.mcpb as a release asset (#84) (28cd12a), closes #46 #45 #43 #40 #47

v2.2.7 · 2026-08-17

2.2.7 (2026-08-17) · make OAuth scopes configurable so monitoring-only apps work

04 · Who maintains Ninja One

NinjaOne is maintained by wyre-technology. We track 57 MCP servers from wyre-technology - 57 actively maintained, 150 combined GitHub stars, oldest repo from Jun 2025. Full record: all servers from wyre-technology.

  1. Autotask MCP server for Kaseya Autotask PSA - companies, tickets, projects, time entries, and more. ★ 48
  2. ConnectWise Manage MCP server for ConnectWise Manage PSA - companies, tickets, projects, time entries, and more. ★ 20
  3. IT Glue MCP server for IT Glue - organizations, configurations, passwords, flexible assets, and documents. ★ 17
  4. CIPP MCP server for CIPP - M365 multi-tenant management for MSPs (users, tenants, policies). ★ 10
  5. Datto RMM MCP server for Datto RMM - devices, alerts, sites, jobs, and audit data. ★ 3
  6. HaloPSA MCP server for HaloPSA - clients, tickets, and PSA workflows via the HaloPSA REST API. ★ 3

05 · Facts

category
DevOps & monitoring - ranked #83 of 101 actively-maintained DevOps & monitoring servers as of 2026-08-25.
release cadence
10+ releases in the last 90 days (latest 2026-08-21)
registry
io.github.wyre-technology/ninjaone-mcp (active, first published 2026-04-29 · 26 versions)
packages
oci:ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9

06 · Ninja One FAQ

What is Ninja One?

A Model Context Protocol (MCP) server for interacting with NinjaOne, featuring a decision tree architecture for efficient tool loading.

Is Ninja One still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-24 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install Ninja One?

Run `docker run -i --rm ghcr.io/wyre-technology/ninjaone-mcp:v2.2.9`. The README documents 5 environment variables (NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, NINJAONE_REGION…) to set first. Set NINJAONE_CLIENT_ID, NINJAONE_CLIENT_SECRET, NODE_AUTH_TOKEN before connecting. NINJAONE_REGION, NINJAONE_SCOPES are optional or environment-specific per the README. You can also paste the ready-made client config above.

07 · Alternatives to Ninja One

More DevOps & monitoring MCP servers · LLM Usage · VMware AIops · VMware Monitor · ReNoUn - Crypto Regime Classification · Agent Lens

More TypeScript MCP servers · Proofpoint · QuickBooks Online (wyre-technology) · Super Ops · Syncro · Codex MCP Tool · see all