LibreNMSSAFE
MCP server for LibreNMS management
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
LibreNMS MCP Server is a Python-based Model Context Protocol (MCP) server designed to provide advanced, programmable access to LibreNMS network monitoring data and management features. It exposes a modern API for querying, automating, and integrating LibreNMS resources such as devices, ports, alerts, inventory, locations, logs, and more. The server supports both read and write operations, robust security features, and is suitable for integration with automation tools, dashboards, and custom network management workflows.
Features
Core Features
- Query LibreNMS devices, ports, inventory, locations, logs, and alerts with flexible filtering
- Retrieve network topology, device status, and performance metrics
- Access and analyze alert history, event logs, and system health
- Monitor interface statistics, port status, and traffic data
- Track endpoints and connected devices by MAC or IP address
- Retrieve and manage device groups, port groups, and poller groups
- Get detailed information about network services and routing
Management Operations
- Create, update, and delete devices, ports, and groups (if enabled)
- Manage alert rules, notifications, and device metadata
- Configure read-only mode to restrict all write operations for safe monitoring
- Support for bulk operations on devices and ports
Advanced Capabilities
- Rate limiting and API security features
- Real-time network monitoring and health tracking
- Comprehensive logging and audit trails
- SSL/TLS support and configurable timeouts
- Optional tool-search transform for large tool catalogs
- Extensible with custom middlewares and utilities
Installation
Prerequisites
- Python 3.11 to 3.14
- Access to a LibreNMS
- Valid LibreNMS token with appropriate permissions
Quick Install from PyPI
The easiest way to get started is to install from PyPI:
# Using UV (recommended) uvx librenms-mcp # Or using pip
cf4d2816aa13OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add librenms-mcp --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} -- uvx librenms-mcp==1.11.3claude mcp add librenms-mcp --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} -- uvx librenms-mcp==1.11.3claude mcp add librenms-mcp:1.11.3 --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} --env LIBRENMS_TOKEN=${LIBRENMS_TOKEN} -- docker run -i --rm ghcr.io/mhajder/librenms-mcp:1.11.3:NoneExposed tools (4)
2 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
alert_rule_edit | write | - rule_id (required): Rule ID to edit |
alert_template_edit | write | - template_id (required): Template ID to edit. Without it LibreNMS creates a new |
ping | read | |
system_info | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (3)
CMD wget --no-verbose --tries=1 --spider http://127.0.0.1:8000/openapi.json || exit 1
.pre-commit-config.yaml
.release-please-manifest.json
Gates applied: no_behavioural_pass.
cf4d2816aa13full audit observations/trust-audit/mcp-server/mhajder__librenms.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | cf4d2816aa13 | SAFE | B | 89 | first audit |
Questions
What is the LibreNMS MCP server?
MCP server for LibreNMS management
What tools does LibreNMS expose?
4 in total: 2 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is LibreNMS safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does LibreNMS need?
It reads LIBRENMS_TOKEN and MCP_HTTP_BEARER_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does LibreNMS run?
It speaks sse, stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as librenms-mcp.
How current is this page?
The grade is for one exact copy of the source (cf4d2816aa13), read on 2026-10-08. The repository is watched and re-audited when it changes.