Ext Ops Panel
Open dashboard
Comparison

LibreNMS MCP vs ParkPow MCP by usefulapi

LibreNMS MCP is an MCP server published by mhajder. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). ParkPow MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceLibreNMS MCPParkPow MCP by usefulapi
Official MCP Registry Listed
Version: 1.13.0
Downloads/month (PyPI): 1 408
Downloads/week (PyPI): 503
Forks (GitHub): 11
Stars (GitHub): 42
Not marked · First seen
Listed
Version: 1.0.2
No figure published
Not marked · First seen
PyPI (MCP servers) Listed
Version: 1.13.0
Downloads/month (PyPI): 1 408
Downloads/week (PyPI): 503
Forks (GitHub): 11
Stars (GitHub): 42
Not marked · First seen
Not listed

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

LibreNMS MCP vs ParkPow MCP by usefulapi
FactLibreNMS MCPParkPow MCP by usefulapi
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)42No figure on GitHub
Forks (GitHub) (differs)11No figure on GitHub
Last release (differs)2026-11-07 (worse)2026-11-07 (better)
Where it runs (differs)On your machine (librenms-mcp)Remote server (parkpow.usefulapi.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)26, secrets among them: 3Not published
LicenceNot statedNot stated
Repository (differs)github.com/mhajder/librenms-mcpgithub.com/m190/usefulapi-mcp
Changes in the last 7 days (differs)34
First seen (differs)2026-10-112026-11-07
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

LibreNMS MCP

In its own words, on Official MCP Registry:

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

ParkPow MCP by usefulapi

In its own words, on Official MCP Registry:

Read vehicles, visits and occupancy; edit vehicle records and tags, and add comments in ParkPow.

How to run each

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)

ParkPow MCP by usefulapi As a remote MCP server

Claude Code
claude mcp add --transport http parkpow https://parkpow.usefulapi.io/mcp

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

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 ParkPow MCP by usefulapi publish no settings it asks for, so we do not compare settings.

What it can do: LibreNMS MCP · What it can do: ParkPow MCP by usefulapi · 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