Skip to main content
Glama
Allied-Business-Solutions

NinjaOne MCP Server

by Allied-Business-Solutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to NinjaOne MCP Server

No user-submitted related servers found.

    Related Servers

    • ninjaone-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for the NinjaOne RMM platform, enabling tools to manage devices, organizations, alerts, jobs, and policies through NinjaOne's API.
      26
      Apache 2.0

    • mcp-ninjaone

      fredriksknese
      F
      license
      A
      quality
      C
      maintenance
      An MCP server that connects AI assistants to the NinjaOne remote monitoring and management platform via the REST API v2. It provides tools for device inventory, organization management, alert handling, maintenance scheduling, and automated job execution.
      22
      1
      -

    • ninjaone-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for NinjaOne RMM that exposes tools for managing organizations, devices, alerts, ticketing, and automation/scripting via NinjaOne's Public API v2.
      -

    • MSP360 MCP

      tonyzorin
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for MSP360 platform enabling management of backup and RMM operations through Claude Desktop with 69 tools.
      MIT

    • action1-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Action1, a cloud-native RMM platform, enabling remote monitoring, patch management, and endpoint management through Action1's API.
      6
      2
      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.9/5.0

    Scored across 96 tools

    Disambiguation2/5

    The tool set is very large (96 tools) with many overlapping verb-noun pairs like 'getting' versus 'querying' device details. Agents may struggle to distinguish between similar tools such as 'ninja_get_device_os_patches' and 'ninja_query_os_patches', leading to potential misselection.

    Naming Consistency4/5

    All tools consistently follow the pattern 'ninja_verb_noun' (e.g., ninja_create_organization, ninja_list_devices). However, there is slight variation in verb choice (e.g., 'submit' vs 'apply' for patching actions), which is minor.

    Tool Count2/5

    With 96 tools, the server is over-saturated. While the RMM domain is broad, this many tools overwhelm agents and increase cognitive load. A more curated set (20-40) would improve usability.

    Completeness4/5

    The tool set covers most major aspects of device management, ticketing, patching, and querying. Notable gaps include no delete operations for tickets or organizations, but the surface is otherwise comprehensive for typical RMM tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources