Skip to main content
Glama
fredriksknese

mcp-ninjaone

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-ninjaone

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

    • 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.
      -

    • kaseya-vsa-mcp

      WYRE-AI
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Kaseya VSA — endpoints, patches, procedures, alarms, and tickets. Enables AI assistants to manage and monitor devices via the Kaseya VSA RMM platform.
      Apache 2.0

    • trmm-mcp

      shin2344234
      A
      license
      B
      quality
      A
      maintenance
      MCP server that gives AI assistants read-only access to TacticalRMM fleet data (agents, checks, alerts, services, processes, etc.) and, with explicit approval, lets them run commands on managed machines.
      20
      2
      AGPL 3.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

    A3.6/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Tools like list_alerts and list_device_alerts are clearly differentiated by scope (global vs. per-device). No overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., get_device, list_organizations, create_maintenance_window). No mixing of styles like camelCase or inconsistent verbs.

    Tool Count4/5

    22 tools is slightly above the typical well-scoped range (3-15) but justified given the breadth of RMM functionality covered (devices, alerts, maintenance, organizations, scripts).

    Completeness3/5

    Covers many key operations for device and alert management, but lacks full CRUD for devices, organizations, and scripts (e.g., no create_device, update_organization, or delete_script). Notable gaps in lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources