MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure
Most database access work still happens through a UI a human drives. LibreNMS MCP MCP server moves it into the conversation instead. MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure.
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.
The server publishes 14 tools. What each one is for:
devices_list — List all devices (with optional filters)device_get — Get details for a specific devicedevice_add — Add a new devicedevice_update — Update device metadatadevice_delete — Remove a devicedevice_ports — List all ports for a devicedevice_ports_get — Get details for a specific port on a devicedevice_fdb — List the forwarding database (learned MACs) for a devicedevice_nac — List network access control (802.1X / MAB) sessions on a devicedevice_availability — Get device availabilitydevice_outages — Get device outagesdevice_set_maintenance — Set device maintenance modeInstallation goes through your MCP client rather than a global install: point it at librenms-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: LIBRENMS_URL, LIBRENMS_TOKEN, SENTRY_DSN, MCP_HTTP_HOST, MCP_HTTP_BEARER_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. LibreNMS MCP's toolset — devices_list, device_get, device_add and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mhajder; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against LibreNMS MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| devices_list | List all devices (with optional filters) |
| device_get | Get details for a specific device |
| device_add | Add a new device |
| device_update | Update device metadata |
| device_delete | Remove a device |
| device_ports | List all ports for a device |
| device_ports_get | Get details for a specific port on a device |
| device_fdb | List the forwarding database (learned MACs) for a device |
| device_nac | List network access control (802.1X / MAB) sessions on a device |
| device_availability | Get device availability |
| device_outages | Get device outages |
| device_set_maintenance | Set device maintenance mode |
| device_discover | Discover or add a device using provided credentials |
| device_rename | Rename an existing device |
{
"mcpServers": {
"librenms": {
"command": "uvx",
"args": ["librenms-mcp"],
"env": {
"LIBRENMS_URL": "your-value",
"LIBRENMS_TOKEN": "your-value",
"SENTRY_DSN": "your-value",
"MCP_HTTP_HOST": "your-value",
"MCP_HTTP_BEARER_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| LIBRENMS_URL | Endpoint or connection string the server talks to. | Yes |
| LIBRENMS_TOKEN | Credential the server authenticates with. | Yes |
| SENTRY_DSN | Endpoint or connection string the server talks to. | Yes |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_HTTP_BEARER_TOKEN | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.