Skip to main content
Glama
dmayan-ss

mcp-prtg

by dmayan-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-prtg

No user-submitted related servers found.

    Related Servers

    • logicmonitor-mcp

      MSPbotsAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the LogicMonitor REST API as MCP tools with per-request LMv1 authentication, enabling querying of devices, alerts, reports, and more.
      Apache 2.0

    • Questrade MCP Server

      DrWheelicus
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying portfolio data, positions, balances, quotes, price history, orders, and account activity through the Questrade API.
      21 npm
      1
      MIT

    • nable-rmm-mcp

      MSPbotsAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with N-able RMM (N-sight) API to manage clients, sites, devices, and retrieve monitoring data such as checks, patches, and performance history.
      Apache 2.0

    • Zabbix MCP Server

      mhajder
      A
      license
      B
      quality
      A
      maintenance
      Provides advanced, programmable access to Zabbix monitoring data and management features, enabling querying, automation, and integration of Zabbix resources.
      53
      112 PyPI
      10
      MIT

    • mcp-nagios-crunchtools

      crunchtools
      A
      license
      A
      quality
      B
      maintenance
      Enables secure interaction with Nagios Core for querying host and service status, acknowledging problems, adding comments, scheduling forced checks, and reading notification history.
      7
      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.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of PRTG monitoring, such as listing groups, devices, sensors, channels, history, and server status. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Most tools follow a consistent 'get_' prefix pattern (e.g., get_sensors, get_groups). The only exception is 'search', which breaks the pattern but is still a clear verb for its purpose.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a PRTG monitoring client. Each tool provides a necessary function without redundancy, covering listing, details, history, and status.

    Completeness4/5

    The tool surface covers core read operations for PRTG monitoring (groups, devices, sensors, channels, history, messages, status, search). Minor gaps exist, such as missing support for thresholds or notifications, but overall it's solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources