Skip to main content
Glama
WYRE-AI

PRTG MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PRTG MCP Server

No user-submitted related servers found.

    Related Servers

    • AlertOps MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Enables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.
      11
      -

    • Prometheus MCP Server

      ArkTechNWA
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query Prometheus metrics, monitor alerts, and analyze system health through read-only access to your Prometheus server with built-in query safety and optional AI-powered metric analysis.
      MIT

    • New Relic MCP Server

      piekstra
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with New Relic monitoring and observability data through programmatic access to New Relic APIs. Supports APM management, NRQL queries, alert policies, synthetic monitoring, dashboards, infrastructure monitoring, and deployment tracking.
      26
      281 PyPI
      6
      MIT

    • Proxmox MCP Server

      teomarcdhio
      A
      license
      A
      quality
      D
      maintenance
      Enables read-only interaction with Proxmox homelab VMs and containers, allowing LLM agents to list VMs, monitor status and performance metrics, view snapshots, and check cluster health through natural language queries.
      8
      MIT

    • Zabbix MCP Server

      initMAX
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes the complete Zabbix API to MCP-compatible AI assistants, enabling natural language management of hosts, problems, and templates across multiple instances. It provides 220 tools for comprehensive monitoring and configuration with support for read-only modes and secure authentication.
      199
      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.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool maps cleanly to a distinct PRTG object type or action: probes, groups, devices, sensors, channels, alarms, and version. The hierarchical relationships are explicit in the descriptions, so there is little risk of selecting the wrong tool.

    Naming Consistency5/5

    All tools follow a consistent `prtg_` + verb + noun pattern, with `list` for collections and `get` for single objects or details. Naming style is uniform snake_case throughout, making the API surface predictable.

    Tool Count5/5

    Fifteen tools is at the upper edge of the ideal range but each one maps to a necessary operation in the PRTG hierarchy. The count is well-scoped for a monitoring-focused server with no redundant or filler tools.

    Completeness4/5

    The read-only monitoring workflow is well covered: navigate probes/groups/devices, list sensors, retrieve channel data, and inspect alarms/status summaries. The main gap is the lack of operational actions like pausing sensors or acknowledging alarms, but those may be intentionally outside the server's scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources