Skip to main content
Glama
Sign In
NinjaOne MCP Server

NinjaOne MCP Server

by SoroushAlamdari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to NinjaOne MCP Server

No user-submitted related servers found.

    Related Servers

    • datto-rmm-mcp

      wylienorthwind
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to interact with Datto RMM accounts for device, alert, site, and quick job management through natural language.
      Apache 2.0

    • NinjaOne MCP Server

      JDelgadoCMG
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of NinjaOne devices, organizations, alerts, and tickets through natural language, using a navigation-based tool selection for efficient interaction.
      Apache 2.0

    • NinjaOne MCP Server

      atiwan
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with NinjaOne through a decision-tree interface for managing devices, organizations, alerts, and tickets via natural language.
      Apache 2.0

    • NinjaOne MCP Server

      KTS-HQ
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with the NinjaOne platform for managing devices, organizations, alerts, and tickets through a decision-tree tool-loading architecture.
      Apache 2.0

    • ninjaone-mcp

      Imburr-BEL
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to interact with NinjaOne, providing tools for managing devices, organizations, alerts, and tickets. Uses a decision tree architecture to load domain-specific tools on demand.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 21 tools

    Disambiguation3/5

    Most specific tools target distinct resources and actions, but generic api_get/api_post overlap with nearly every read/create tool, and list_devices versus search_devices has fuzzy boundaries. Descriptions help, but an agent could reasonably misselect between generic and specific tools or between list and search.

    Naming Consistency4/5

    Nearly all tools use a predictable snake_case verb_noun pattern such as list_devices, get_ticket, create_ticket, and run_script. api_get and api_post are minor deviations since they read as resource_verb rather than verb_resource, but overall the naming is consistent.

    Tool Count4/5

    At 21 tools this is above the typical 3-15 range, but NinjaOne is a broad RMM domain covering devices, alerts, patches, software, tickets, organizations, health, antivirus, and contacts. The tools mostly earn their place, though the generic api_* tools add some redundancy.

    Completeness3/5

    Core areas are covered for devices, alerts, patches, software, tickets, organizations, health, antivirus, and contact listing, but there are notable lifecycle gaps such as no list_tickets, no contact get/create/update/delete, and no organization create/update. The generic api_get/api_post partially mitigate these gaps but do not cover full CRUD because they only expose GET and POST.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources