mcp-prtg
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-prtg show sensors with status 'Warning'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-prtg
MCP Server for PRTG Network Monitor (read-only).
Allows Claude to query sensors, devices, groups, channels, historical data, and system status from your PRTG instance via the classic PRTG HTTP API (v1). Supports self-signed SSL certificates.
Note: This server uses the classic PRTG API (
/api/table.json,/api/historicdata.json, etc.), which is available in all PRTG versions. PRTG also offers a newer REST API v2 (available since v21.4.73 on port 1616) that is not yet supported by this server.
Authentication
This server authenticates using username + passhash. API tokens and plaintext passwords are not supported.
Getting your passhash
Open this URL in your browser (replace with your PRTG server, user, and password):
https://prtg.example.com/api/getpasshash.htm?username=myuser&password=mypasswordRelated MCP server: PA MCP Server
Configuration in Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"prtg": {
"command": "uv",
"args": ["--directory", "/path/to/mcp-prtg", "run", "server.py"],
"env": {
"PRTG_URL": "https://prtg.example.com",
"PRTG_USERNAME": "apiuser",
"PRTG_PASSHASH": "1234567890"
}
}
}
}Environment Variables
Variable | Required | Description |
| Yes | URL of your PRTG server (e.g., |
| Yes | PRTG username for authentication |
| Yes | Passhash for the PRTG user |
Available Tools
Tool | Description |
| List sensors with filters (status, tags, parent ID, text) |
| Full details for a specific sensor |
| List channels for a sensor |
| List devices with filters |
| List groups (used to organize devices) |
| Historic monitoring data for a sensor |
| Overall PRTG server health and sensor counts |
| System log messages with optional date range filter |
| Search objects by name across sensors, devices, or groups |
Development
# Install dependencies
uv sync
# Run the server locally
PRTG_URL=https://prtg.local PRTG_USERNAME=admin PRTG_PASSHASH=12345 uv run server.py
# Test with MCP Inspector
npx @modelcontextprotocol/inspector uv run server.pyLicense
MIT
Available Tools
9 toolsget_channelsB
List all channels for a specific sensor.
Args: id: The sensor object ID.
Inputs: id (required). Returns: result
get_devicesA
List PRTG devices with optional filters.
Args: id: Parent group ID to list devices under. text_filter: Filter devices whose name contains this text. count: Max results (default 500).
Inputs: id, count, text_filter. Returns: result
get_groupsA
List PRTG groups (used to organize devices).
Args: id: Parent group ID to list sub-groups under. count: Max results (default 500).
Inputs: id, count. Returns: result
get_messagesA
Get PRTG system log messages.
Args: id: Object ID to filter messages for. count: Max messages (default 100). date_range: Relative date filter: today, yesterday, 7days, 30days, 6months, 12months.
Inputs: id, count, date_range. Returns: result
get_sensor_detailsB
Get full details for a specific sensor.
Args: id: The sensor object ID.
Inputs: id (required). Returns: result
get_sensor_historyA
Get historic monitoring data for a sensor.
Args: id: The sensor object ID. sdate: Start date/time as YYYY-MM-DD-HH-MM-SS. edate: End date/time as YYYY-MM-DD-HH-MM-SS. avg: Averaging interval in seconds. 0=raw, 300=5min, 3600=1h, 86400=1day. count: Max data points (default 500).
Inputs: id (required), edate (required), sdate (required), avg, +1 more. Returns: result
get_sensorsA
List PRTG sensors with optional filters.
Args: id: Parent object ID (device or group) to filter sensors under. status: Filter by status: up, down, warning, paused, unknown, unusual, down_acknowledged, down_partial. tags: Filter by tag, e.g. @tag(mytag). text_filter: Filter sensors whose name contains this text. count: Max results (default 500).
Inputs: id, tags, count, status, +1 more. Returns: result
get_server_statusA
Get overall PRTG server health and sensor counts.
Inputs: no named parameters. Returns: result
searchA
Search PRTG objects by name.
Args: query: Text to search for in object names. type: Object type: sensors, devices, or groups. count: Max results (default 50).
Inputs: query (required), type, count. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
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.
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.
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.
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
Related MCP Connectors
Query and manage SquaredUp dashboards, data streams, the knowledge graph, and KPIs (EU region).
Read pages, components, incidents and maintenances; create and update incidents in Statuspage.
Query and manage SquaredUp dashboards, data streams, the knowledge graph, and KPIs (US region).
List devices, alerts, antivirus status and audit logs, and run scripts on devices in Pulseway.
Related MCP Servers
- AlicenseBqualityBmaintenanceProvides advanced, programmable access to Zabbix monitoring data and management features, enabling querying, automation, and integration of Zabbix resources.53276 PyPI11MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Palo Alto Networks firewalls via XML API for configuration and monitoring tasks.-
- FlicenseNot gradedqualityCmaintenanceEnables querying portfolio data, positions, balances, quotes, price history, orders, and account activity through the Questrade API.1-
- AlicenseNot gradedqualityCmaintenanceEnables 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