LibreNMS MCP

LibreNMS MCP runs locally from a Python package published to PyPI: librenms-mcp version 1.11.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx librenms-mcp. It reads these environment variables: LIBRENMS_URL (required), LIBRENMS_TOKEN (required, secret), LIBRENMS_VERIFY_SSL, LIBRENMS_TIMEOUT, READ_ONLY_MODE, DISABLED_TAGS, LOG_LEVEL, RATE_LIMIT_ENABLED, RATE_LIMIT_MAX_REQUESTS, RATE_LIMIT_WINDOW_MINUTES, TOOL_SEARCH_ENABLED, TOOL_SEARCH_STRATEGY and TOOL_SEARCH_MAX_RESULTS; set them in the client's configuration for this server.

LibreNMS MCP runs locally from a Python package published to PyPI: librenms-mcp version 1.11.2. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names uvx as the runtime). It reads these environment variables: LIBRENMS_URL (required), LIBRENMS_TOKEN (required, secret), LIBRENMS_VERIFY_SSL, LIBRENMS_TIMEOUT, READ_ONLY_MODE, DISABLED_TAGS, LOG_LEVEL, RATE_LIMIT_ENABLED, RATE_LIMIT_MAX_REQUESTS, RATE_LIMIT_WINDOW_MINUTES, TOOL_SEARCH_ENABLED, TOOL_SEARCH_STRATEGY, TOOL_SEARCH_MAX_RESULTS, MCP_HTTP_PORT, MCP_HTTP_BEARER_TOKEN (secret) and MCP_TRANSPORT; set them in the client's configuration for this server.

LibreNMS MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/mhajder/librenms-mcp:1.11.2. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL. It reads these environment variables: LIBRENMS_URL (required), LIBRENMS_TOKEN (required, secret), LIBRENMS_VERIFY_SSL, LIBRENMS_TIMEOUT, READ_ONLY_MODE, DISABLED_TAGS, LOG_LEVEL, RATE_LIMIT_ENABLED, RATE_LIMIT_MAX_REQUESTS, RATE_LIMIT_WINDOW_MINUTES, TOOL_SEARCH_ENABLED, TOOL_SEARCH_STRATEGY, TOOL_SEARCH_MAX_RESULTS, SENTRY_DSN (secret), SENTRY_TRACES_SAMPLE_RATE, SENTRY_SEND_DEFAULT_PII, SENTRY_ENVIRONMENT, SENTRY_RELEASE, SENTRY_PROFILE_SESSION_SAMPLE_RATE and SENTRY_PROFILE_LIFECYCLE; set them in the client's configuration for this server. Required arguments: -p.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "librenms-mcp": {
      "command": "uvx",
      "args": [
        "librenms-mcp"
      ],
      "env": {
        "LIBRENMS_URL": "<value>",
        "LIBRENMS_TOKEN": "<secret>",
        "LIBRENMS_VERIFY_SSL": "<value>",
        "LIBRENMS_TIMEOUT": "<value>",
        "READ_ONLY_MODE": "<value>",
        "DISABLED_TAGS": "<value>",
        "LOG_LEVEL": "<value>",
        "RATE_LIMIT_ENABLED": "<value>",
        "RATE_LIMIT_MAX_REQUESTS": "<value>",
        "RATE_LIMIT_WINDOW_MINUTES": "<value>",
        "TOOL_SEARCH_ENABLED": "<value>",
        "TOOL_SEARCH_STRATEGY": "<value>",
        "TOOL_SEARCH_MAX_RESULTS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect