LibreNMS MCP

What this does

LibreNMS MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

LIBRENMS_URL
LIBRENMS_TOKEN
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

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install LibreNMS MCP?

Run the Claude Code command in the install section to add LibreNMS MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with LibreNMS MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to LibreNMS MCP as well.

Does LibreNMS MCP need an API key?

Yes. Before it can run, set these environment variables: LIBRENMS_URL, LIBRENMS_TOKEN, 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. They go in the env block of your MCP config.