# librenmsctrl MCP server

> Allows an AI client to inspect LibreNMS devices, ports, alerts, and event logs with gated write capabilities for safe network monitoring.

- Repository: https://github.com/lidless-labs/librenmsctrl
- Page: https://hostedmcp.org/servers/lidless-labs/librenmsctrl
- Transport: —
- Stars: 1
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `LIBRENMS_TLS_INSECURE` | no | no |  |
| `LIBRENMS_TOKEN` | no | no |  |
| `LIBRENMS_URL` | no | no |  |

## Tools (13)

- `librenms_status`
- `librenms_list_devices`
- `librenms_get_device`
- `librenms_list_ports`
- `librenms_get_port`
- `librenms_port_health`
- `librenms_list_alerts`
- `librenms_get_alert`
- `librenms_alert_history`
- `librenms_event_log`
- `librenms_ack_alert`
- `librenms_unmute_alert`
- `librenms_set_maintenance`

## FAQ

### How does the server prevent accidental changes to my monitoring state?

The server uses a three-tier write-gating pattern where safe writes require an explicit 'confirm: true' argument and all inputs are schema-validated before execution.

### What kind of write operations are supported in version 1?

Version 1 supports 'safe writes' such as acknowledging alerts, unmuting alerts, and putting devices into maintenance windows, but destructive operations like device deletion are not yet implemented.

### What environment variables are required to run the server?

You must set both LIBRENMS_URL and LIBRENMS_TOKEN to connect to your instance.
