NinjaOne MCP server

What the model can do

NinjaOne remote monitoring and management: client organisations, devices with online state and maintenance, a device's scripts and Windows services, active alerts, the activity log, pending patches, and tickets by board with their history. When you ask, can create, update and comment on tickets, reset alerts, schedule or cancel maintenance, reboot devices, run scripts, scan for and apply patches, start or stop Windows services, create organisations, rename or move devices, approve or reject new devices, and decommission devices.

Reads

• ninjaone_list_organizationsClient organisations in NinjaOne: id, name, description and how new devices are approved.
• ninjaone_list_devicesDevices: name, class (Windows server, Mac, network device and so on), organisation, online or offline, last contact, approval and maintenance state…
• ninjaone_get_deviceOne device in full: name, class, organisation and location, operating system, make and model, IP addresses, online state, maintenance, plus…
• ninjaone_list_alertsActive alerts (triggered conditions): which device, what tripped (offline, CPU, disk space and so on), the message, and when.
• ninjaone_list_activitiesThe activity log, newest first: conditions triggered and reset, scripts and actions run, patches installed, devices and users created, with status…
• ninjaone_list_patchesOperating system patches that are pending, failed or rejected across devices: patch name, KB number, severity, status and device.
• ninjaone_list_ticketsTickets on a NinjaOne ticket board: id, subject, status, priority, organisation, assignee and the board's other columns, with a text search.
• ninjaone_get_ticketOne ticket with its history: subject, status, priority, severity, organisation, device, assignee and tags, and its log entries (comments…

Acts, when you ask

These change something in NinjaOne. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• ninjaone_create_ticketCreates a ticket in NinjaOne for a client organisation, with a description that is public (the requester can see it) or internal.
• ninjaone_update_ticketChanges a NinjaOne ticket's subject, status, priority, severity, type, assignee or tags; only what is passed changes…
• ninjaone_comment_ticketAdds a comment to a NinjaOne ticket.
• ninjaone_reset_alertResets (clears) an active NinjaOne alert, so it leaves the alert list until the condition trips again.
• ninjaone_schedule_maintenancePuts a NinjaOne device into a maintenance window, switching off the features you name (alerts, patching, antivirus scans…
• ninjaone_cancel_maintenanceCancels a NinjaOne device's pending or active maintenance window, so alerts, patching and tasks resume.
• ninjaone_reboot_deviceRestarts a NinjaOne-managed computer now.
• ninjaone_run_scriptRuns a script or built-in action on a NinjaOne-managed device, as the credential you name…
• ninjaone_scan_patchesStarts a patch scan on a NinjaOne device, for operating system or third-party software patches, so its pending patch list is current.
• ninjaone_apply_patchesInstalls the approved operating system or software patches on a NinjaOne device now, by its patch policy.
• ninjaone_control_serviceStarts, stops, pauses or restarts a Windows service on a NinjaOne device; stopping one stops whatever depends on it for its users.
• ninjaone_create_organizationCreates a client organisation in NinjaOne, optionally with locations, optionally copying settings from a template organisation.
• ninjaone_update_deviceRenames a NinjaOne device or moves it to another organisation, location, role or policy; moving it changes which policy (monitoring, patching…
• ninjaone_approve_devicesApproves or rejects devices waiting for approval in NinjaOne, by id.
• ninjaone_decommission_deviceDecommissions a NinjaOne device: it stops being monitored and managed and its agent is removed.

Connect it

First connect NinjaOne on Dashboard → Connections, then add Memtro to your client once. The NinjaOne tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared NinjaOne connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which devices at Acme Ltd are offline right now?
• › What alerts are active on the file server?
• › Which critical patches are still pending?
• › What happened on ticket 4821 since yesterday?
• › Reboot the reception PC at Northwind.

Questions

Is this an official NinjaOne MCP server?

No. It is Memtro's MCP server with Memtro's NinjaOne connector behind it: the connector reads NinjaOne through its API with the credentials you connect on Dashboard → Connections, and NinjaOne publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in NinjaOne?

Only when you ask, and only what it has been granted: create a ticket; update a ticket's subject, status, priority, severity, type, assignee or tags; comment on a ticket (a public comment may email the requester); reset an alert; schedule a maintenance window on a device; cancel a device's maintenance window; reboot a device; run a script or built-in action on a device; scan a device for operating system or software patches; install a device's approved operating system or software patches; start, stop, pause or restart a Windows service on a device; create a client organisation; rename a device or move it to another organisation, location, role or policy; approve or reject devices waiting for approval; decommission a device. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server