Ext Ops Panel
Open dashboard
Comparison

Nodle IoT Dashboard vs LibreNMS MCP

Nodle IoT Dashboard is an MCP server published by nodle.com. Marketplaces we read that list it: 1 (Official MCP Registry). LibreNMS MCP is an MCP server published by mhajder. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceNodle IoT DashboardLibreNMS MCP
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.13.0
Downloads/month (PyPI): 1 408
Downloads/week (PyPI): 503
Forks (GitHub): 11
Stars (GitHub): 42
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.13.0
Downloads/month (PyPI): 1 408
Downloads/week (PyPI): 503
Forks (GitHub): 11
Stars (GitHub): 42
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Nodle IoT Dashboard vs LibreNMS MCP
FactNodle IoT DashboardLibreNMS MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub42
Forks (GitHub) (differs)No figure on GitHub11
Last release (differs)Not published2026-11-07
Where it runs (differs)Remote server (dashboard.nodle.com/api/mcp)On your machine (librenms-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published26, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/mhajder/librenms-mcp
Changes in the last 7 days (differs)23
First seen (differs)2026-11-042026-10-11
Endpoint at the last check (differs)Responded 20 h ago, requires authenticationno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Nodle IoT Dashboard

In its own words, on Official MCP Registry:

Fleets, devices, detections and webhooks on the Nodle Bluetooth Low Energy network.

LibreNMS MCP

In its own words, on Official MCP Registry:

MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure

How to run each

Nodle IoT Dashboard As a remote MCP server

Claude Code
claude mcp add --transport http iot-dashboard https://dashboard.nodle.com/api/mcp

LibreNMS MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LIBRENMS_TOKEN=<YOUR_LIBRENMS_TOKEN>" --env "LIBRENMS_URL=<YOUR_LIBRENMS_URL>" --env "MCP_HTTP_BEARER_TOKEN=<YOUR_MCP_HTTP_BEARER_TOKEN>" --env "SENTRY_DSN=<YOUR_SENTRY_DSN>" --transport stdio librenms-mcp -- uvx librenms-mcp

Requires: LIBRENMS_TOKEN (secret), LIBRENMS_URL, MCP_HTTP_BEARER_TOKEN (secret), SENTRY_DSN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Nodle IoT Dashboard has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Nodle IoT Dashboard publish no settings it asks for, so we do not compare settings.

What it can do: Nodle IoT Dashboard · What it can do: LibreNMS MCP · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built