clr-librenms-mcp

MCP server for LibreNMS network monitoring — query devices, alerts, sensors, ports, and more through AI assistants like Claude.

Features

• Device monitoring — list devices, health summary, availability, outages, down devices
• Alert management — list, filter, acknowledge alerts, alert rules
• Sensor data — health sensors by device and type (temperature, voltage, fan, etc.)
• Port/interface info — list ports, search by name, find by MAC address
• ARP & FDB lookups — resolve IPs to MACs, find MAC on switch ports
• Hardware inventory — chassis, modules, power supplies, serial numbers
• IP address management — list IPs assigned to devices
• Token-based auth — simple X-Auth-Token authentication

Installation

pip install clr-librenms-mcp
# or
uvx clr-librenms-mcp

Configuration

Preferred: Configuration file at ~/.config/librenms/credentials.json (chmod 600):

{
  "url": "https://librenms.example.com",
  "token": "your-api-token"
}

Alternative: Environment variables are also supported:

Optional:

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "librenms": {
      "command": "uvx",
      "args": ["clr-librenms-mcp"]
    }
  }
}

Claude Code

Add via CLI:

claude mcp add librenms -- uvx clr-librenms-mcp

Or add to your .mcp.json:

{
  "librenms": {
    "command": "uvx",
    "args": ["clr-librenms-mcp"]
  }
}

VS Code

Add to your VS Code settings or .vscode/mcp.json:

{
  "mcp": {
    "servers": {
      "librenms": {
        "command": "uvx",
        "args": ["clr-librenms-mcp"]
      }
    }
  }
}

Note: Configuration is read from ~/.config/librenms/credentials.json or environment variables. No need to specify credentials in MCP config files.

HTTP Transport

To run as a standalone HTTP server:

clr-librenms-mcp --transport http --host 0.0.0.0 --port 8000

Tools

System

Devices

Alerts

Alert filter values:

Sensors & Health

Health types: temperature, voltage, fanspeed, power, humidity, state, and more.

Ports & Interfaces

Network Lookups

Example Usage

Once connected, you can ask your AI assistant things like:

• "Are any devices down in LibreNMS?"
• "Show me all critical alerts"
• "What are the temperature sensors on router01?"
• "Find which switch port has MAC aa:bb:cc:dd:ee:ff"
• "What's the availability for switch01 over the last 30 days?"
• "Acknowledge alert 42"
• "Show me the ARP table for 10.0.0.0/24"
• "List the hardware inventory for core-switch"

Safety

All tools are read-only except librenms_ack_alert, which is a non-destructive write operation — it marks an alert as acknowledged but does not modify device configuration or monitoring state.

Technical Notes

• Auth: Token-based via X-Auth-Token header (generate tokens in LibreNMS under API Settings)
• API version: Uses LibreNMS REST API v0
• Device parameter: Most tools accept hostname, IP address, or device_id interchangeably
• Sensors: Use librenms_device_health with health_type for filtered sensor views, or librenms_list_sensors for all sensors across all devices

Development

git clone https://github.com/clearminds/clr-librenms-mcp.git
cd clr-librenms-mcp
uv sync
uv run clr-librenms-mcp

License

MIT — see LICENSE for details.