$ cat ~/map/pi-librenms.md

pi-librenms

LibreNMS network-monitoring tools for pi: devices, ports, alerts, and Oxidized configs over the REST API, no MCP layer.

extensions✓ Sep 22

pi install git:github.com/ninjaltd/pi-librenms (or install by URL), then restart pi or run /reload; configure via LIBRENMS_URL and LIBRENMS_TOKEN environment variables, a PI_LIBRENMS_CONFIG file, the default ~/.config/pi-librenms/config.env, or a project-local .pi/librenms.json

## TL;DR

pi-librenms adds twenty LibreNMS tools to pi so the agent can check devices, ports, outages, syslog, alerts, BGP sessions, inventory, and Oxidized configs over the LibreNMS REST API — no MCP layer, configured with LIBRENMS_URL and an API token.

## Key points

• $Monitoring coverage: librenms_ping verifies connectivity and the token; device listings filter up, down, or all; per-device tools cover ports, outage history, event log, and syslog search; a port lookup by ID and a MAC-address search round out the interface side.
• $Alert and inventory surfaces: current and historical alerts, device locations, device groups, and hardware inventory spanning components, modules, and chassis.
• $BGP and Oxidized: all BGP sessions plus per-session detail, alongside the Oxidized trio — devices tracked, latest backed-up config per device, and a search across all stored configs by string.
• $The guarded write path: device_maintenance_status reports whether a device sits in a maintenance window, and device_maintenance puts one in — asking for confirmation before acting.
• $Configuration resolves in a documented first-hit-wins order: environment variables, then the PI_LIBRENMS_CONFIG file path, then the default config.env under ~/.config/pi-librenms, then a project-local .pi/librenms.json.
• $No MCP layer: the extension calls the LibreNMS REST API directly — the README frames the whole stack as pi, an extension, and a read API token.

## FAQ

## References

• README ↗

Last updated: Sep 22, 2026