Skip to main content
Glama
am3cramirez

saas-alerts-mcp

by am3cramirez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to saas-alerts-mcp

No user-submitted related servers found.

    Related Servers

    • saas-alerts-mcp

      WYRE-AI
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Kaseya SaaS Alerts, providing tools to query security events, manage customers/users, handle devices, billing, reports, and partner settings via the External Partner API.
      -

    • 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

    • acronis-mcp

      MSPbotsAI
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes Acronis Cyber Protect Cloud APIs as 14 read-only tools for managing alerts, tasks, agents, resources, policies, and tenants.
      -

    • superops-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for SuperOps PSA/RMM, enabling MSPs to manage tickets, assets, clients, and field technician operations through SuperOps's API.
      22
      3
      Apache 2.0

    • 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
    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 30 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: customers, devices, events, billing, reports, and partner operations are all separated. Even similar tools like events_query and events_query_advanced are differentiated by the use of raw Elasticsearch versus standard filters. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow the consistent pattern 'saas_alerts_<resource>_<action>', using snake_case throughout. Actions like list, get, create, update, delete, and set are used predictably. The few top-level tools (navigate, status) still retain the 'saas_alerts' prefix and are easy to understand.

    Tool Count2/5

    With 30 tools, the server exceeds the 25+ threshold that indicates an overly large tool set. The broad scope of SaaS Alerts management justifies many tools, but there is some redundancy (e.g., multiple device list tools and separate navigation/status tools) that could be consolidated.

    Completeness2/5

    Customer CRUD is well covered, but there are significant gaps: devices have only list operations (no mapping or ignoring actions), scheduled reports lack an update tool, and users have no management beyond listing. These missing operations create dead ends for agents trying to perform common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources