Librenms MCP

MCPAI代理

提供方 未标注

AI代理 SSE · 服务端推送 Token 社区 / 第三方
查看接入方式

全面解析Librenms MCPMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Librenms MCP能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Librenms MCP 属于AI代理类 MCP 服务器,SSE · 服务端推送,Token,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式SSE · 服务端推送 鉴权Token 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

SSE · 服务端推送 Token
早期远程传输方式,正在被 HTTP 取代
pip install librenms-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Librenms MCP当前 未标注 SSE · 服务端推送 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式SSE · 服务端推送早期远程传输方式,正在被 HTTP 取代
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

22.3 KB
来自项目仓库与上游目录的原文,未做删改

LibreNMS MCP Server

Let AI agents query and manage LibreNMS network monitoring through the Model Context Protocol

Installation · Tools · Configuration · Security

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.

✨ Features

Core Features

  • Query LibreNMS devices, ports, inventory, locations, logs, and alerts with flexible filtering
  • Retrieve network topology, device status, and performance metrics
  • Access and analyze alert history, event logs, and system health
  • Monitor interface statistics, port status, and traffic data
  • Track endpoints and connected devices by MAC or IP address
  • Retrieve and manage device groups, port groups, and poller groups
  • Get detailed information about network services and routing

Management Operations

  • Create, update, and delete devices, ports, and groups (if enabled)
  • Manage alert rules, notifications, and device metadata
  • Configure read-only mode to restrict all write operations for safe monitoring
  • Support for bulk operations on devices and ports

Advanced Capabilities

  • Rate limiting and API security features
  • Real-time network monitoring and health tracking
  • Comprehensive logging and audit trails
  • SSL/TLS support and configurable timeouts
  • Optional tool-search transform for large tool catalogs
  • Extensible with custom middlewares and utilities

🚀 Installation

Prerequisites

  • Python 3.11 to 3.15
  • Access to a LibreNMS
  • Valid LibreNMS token with appropriate permissions

Quick Install from PyPI

The easiest way to get started is to install from PyPI:```sh

Using UV (recommended)

uvx librenms-mcp

Or using pip

pip install librenms-mcp


Remember to configure the environment variables for your LibreNMS instance before running the server:```sh
# Create environment configuration
export LIBRENMS_URL=https://domain.tld:8443
export LIBRENMS_TOKEN=your-librenms-token

For more details, visit: https://pypi.org/project/librenms-mcp/

Install from Source

  1. Clone the repository:```sh
    git clone https://github.com/mhajder/librenms-mcp.git
    cd librenms-mcp

2. Install dependencies:```sh
# Using UV (recommended)
uv sync

# Or using pip
pip install -e .
  1. Configure environment variables:```sh
    cp .env.example .env

Edit .env with your LibreNMS url and token


4. Run the server:```sh
# Using UV (recommended)
uv run librenms-mcp

# Or using the installed command directly
librenms-mcp

Using Docker

A Docker image is available on GitHub Packages for easy deployment. It runs the
HTTP Streamable transport on port 8000 (/mcp).```sh
docker pull ghcr.io/mhajder/librenms-mcp:latest


#### Open WebUI

Open WebUI 0.6.31 and later connect to the image directly; the separate MCPO
image (`ghcr.io/mhajder/librenms-mcpo`) is no longer published. In Open WebUI,
go to **Admin Settings > Integrations > External Tool Servers**, add a connection
of type **MCP (Streamable HTTP)** with the URL `http://:8000/mcp`, and set
Bearer authentication to your `MCP_HTTP_BEARER_TOKEN`.

### Development Setup

For development with additional tools:```sh
# Clone and install with development dependencies
git clone https://github.com/mhajder/librenms-mcp.git
cd librenms-mcp
uv sync --group dev

# Run tests
uv run pytest

# Run with coverage
uv run pytest --cov=src/

# Run linting and formatting
uv run ruff check .
uv run ruff format .

# Run type checking
uv run ty check .

# Setup pre-commit hooks
uv run prek install

🔧 Configuration

Environment Variables

Boolean settings accept true/false, 1/0, yes/no and on/off
(case-insensitive). Any other value stops the server at startup, so a typo
cannot silently turn read-only mode or TLS verification off. The exception is
SENTRY_SEND_DEFAULT_PII and SENTRY_ENABLE_LOGS: when SENTRY_DSN is set, an
invalid value there logs an error and leaves Sentry off, and the server keeps
running.```env

LibreNMS Connection Details

LIBRENMS_URL=https://domain.tld:8443
LIBRENMS_TOKEN=your-librenms-token

SSL Configuration

LIBRENMS_VERIFY_SSL=true
LIBRENMS_TIMEOUT=30

Read-Only Mode

Set READ_ONLY_MODE true to disable all write operations (put, post, delete)

READ_ONLY_MODE=false

Disabled Tags

Comma-separated list of tags to disable tools for (empty by default)

Example: DISABLED_TAGS=alert,alert-rules,alert-templates,bills

DISABLED_TAGS=

Logging Configuration

LOG_LEVEL=INFO

Rate Limiting (requests per minute)

Set RATE_LIMIT_ENABLED true to enable rate limiting

RATE_LIMIT_ENABLED=false
RATE_LIMIT_MAX_REQUESTS=100
RATE_LIMIT_WINDOW_MINUTES=1

Tool Search Transform (Optional)

Set TOOL_SEARCH_ENABLED true to replace full tool listings with search_tools + call_tool

TOOL_SEARCH_ENABLED=false

Search strategy: bm25 (natural language) or regex (pattern match)

TOOL_SEARCH_STRATEGY=bm25

Maximum number of tools returned by search_tools

TOOL_SEARCH_MAX_RESULTS=5

Sentry Error Tracking (Optional)

Set SENTRY_DSN to enable error tracking and performance monitoring

SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789

Optional Sentry configuration

SENTRY_TRACES_SAMPLE_RATE=1.0

SENTRY_SEND_DEFAULT_PII=false

SENTRY_ENVIRONMENT=production

SENTRY_RELEASE=1.2.3

SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0

SENTRY_PROFILE_LIFECYCLE=trace

SENTRY_ENABLE_LOGS=true

MCP Transport Configuration

Transport type: 'stdio' (default), 'sse' (Server-Sent Events), or 'http' (HTTP Streamable).

'streamable-http' is accepted as an alias for 'http'. Any other value stops the server at startup.

MCP_TRANSPORT=stdio

HTTP Transport Settings (used when MCP_TRANSPORT=sse or MCP_TRANSPORT=http)

Host to bind the HTTP server (default: 127.0.0.1)

MCP_HTTP_HOST=127.0.0.1

Port to bind the HTTP server (default: 8000)

MCP_HTTP_PORT=8000

Optional bearer token for authentication (leave empty for no auth)

MCP_HTTP_BEARER_TOKEN=


## 🧰 Available Tools

### Device & Inventory Tools

- `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
- `device_maintenance_status`: Get the maintenance status for a device
- `device_vlans`: List VLANs for a device
- `device_links`: List links for a device
- `device_wireless_sensors`: List wireless sensors (frequency, clients, rssi, ...) with current values
- `device_parents_set`: Set the dependency parents of a device (replaces the current set)
- `device_parents_clear`: Remove dependency parents from a device
- `device_eventlog_add`: Add an event log entry for a device
- `inventory_device`: Get inventory for a device
- `inventory_device_flat`: Get flat inventory for a device
- `devicegroups_list`: List device groups
- `devicegroup_add`: Add a device group
- `devicegroup_update`: Update a device group
- `devicegroup_delete`: Delete a device group
- `devicegroup_devices`: List devices in a device group
- `devicegroup_set_maintenance`: Set maintenance for a device group
- `devicegroup_add_devices`: Add devices to a device group
- `devicegroup_remove_devices`: Remove devices from a device group
- `locations_list`: List all locations
- `location_add`: Add a location
- `location_edit`: Edit a location
- `location_delete`: Delete a location
- `location_get`: Get details for a location
- `location_set_maintenance`: Set maintenance for a location

### Port & Port Group Tools

- `ports_list`: List all ports (with optional filters)
- `ports_search`: Search ports (general search)
- `ports_search_field`: Search ports by a specific field
- `ports_search_mac`: Search ports by MAC address
- `port_get`: Get details for a specific port
- `port_fdb`: List MAC addresses learned on a port
- `port_ip_info`: Get IP address information for a port
- `port_transceiver`: Get transceiver information for a port
- `port_description_get`: Get a port description
- `port_description_update`: Update a port description
- `port_groups_list`: List port groups
- `port_group_add`: Add a port group
- `port_group_list_ports`: List ports in a port group
- `port_group_assign`: Assign ports to a port group
- `port_group_remove`: Remove ports from a port group

### Port Security Tools

- `port_security_list`: List port security configuration across all devices
- `port_security_device`: Get port security configuration for a device
- `port_security_port`: Get port security configuration for a single port

### Graph Tools

Graphs are returned as MCP images. The tools ask LibreNMS for PNG, which MCP
clients such as Claude can display (SVG, LibreNMS's default `webui.graph_type`,
often is not). A LibreNMS release that ignores the request renders in its
`webui.graph_type` format instead; the MIME type is taken from the response.

- `device_graphs_list`: List the graph types available for a device
- `device_graph`: Render a device-level graph (e.g. `device_icmp_perf`)
- `port_graph`: Render a per-port graph by interface name (`bits`, `upkts`, `nupkts`, `errors`, `etherlike`; the LibreNMS names such as `port_bits` are accepted too)
- `port_group_graph`: Render a traffic graph for one or more ports by port ID

Interface names containing a slash (`Te2/7`) are sent percent-encoded, and some
reverse proxies reject or decode the encoded slash. When that happens,
`port_graph` (for `bits`) and `device_ports_get` retry by port ID instead, so
they still work behind such a proxy. Authentication errors are never retried,
and LibreNMS's own "not found" answers are reported as is for names without a
slash (a name with a slash is always retried, since a decoding proxy can turn it
into a LibreNMS "not found" for the wrong path).

Other tools that put a slash-bearing value in the path (`ports_search`,
`ports_search_field`, `oxidized_config_search` with a prefix such as
`0.0.0.0/0`, location names) have no such fallback. If LibreNMS sits
behind Apache, allow encoded slashes so every tool works:```apache
AllowEncodedSlashes NoDecode

A 400 or 404 for a path with an encoded slash that did not come from LibreNMS includes
this hint in the tool's error message.

Alerting & Logging Tools

  • alerts_get: List current and historical alerts
  • alert_get_by_id: Get details for a specific alert
  • alert_acknowledge: Acknowledge an alert
  • alert_unmute: Unmute an alert
  • alert_rules_list: List alert rules
  • alert_rule_get: Get details for a specific alert rule
  • alert_rule_add: Add an alert rule
  • alert_rule_edit: Edit an alert rule
  • alert_rule_delete: Delete an alert rule
  • alert_templates_list: List all alert templates
  • alert_template_get: Get a specific alert template
  • alert_template_create: Create a new alert template
  • alert_template_edit: Edit an alert template
  • logs_eventlog: Get event log for a device, or for all devices when no hostname is given
  • logs_syslog: Get syslog for a device, or for all devices when no hostname is given
  • logs_alertlog: Get alert log for a device, or for all devices when no hostname is given
  • logs_authlog: Get the server-wide authentication log
  • logs_syslogsink: Add a syslog sink

Billing Tools

  • bills_list: List bills
  • bill_get: Get details for a bill
  • bill_graph: Render a bill graph as an image
  • bill_graph_data: Get bill graph data
  • bill_history: Get bill history
  • bill_history_graph: Render a bill history graph as an image
  • bill_history_graph_data: Get bill history graph data
  • bill_create_or_update: Create or update a bill
  • bill_delete: Delete a bill

Oxidized Tools

  • oxidized_list: List devices tracked by Oxidized for config backup
  • oxidized_config_get: Get the stored configuration for a specific device
  • oxidized_config_search: Search all stored device configurations for a string

Network & Monitoring Tools

  • arp_search: Search ARP entries
  • poller_group_get: Get poller group(s)
  • routing_ip_addresses: List all IP addresses from LibreNMS.
  • services_list: List all services from LibreNMS.
  • services_for_device: Get services for a device from LibreNMS.
  • service_add: Add a service to LibreNMS
  • service_edit: Edit an existing service
  • service_delete: Delete a service
  • bgp_sessions: List BGP sessions
  • bgp_session_get: Get details for a specific BGP session
  • bgp_session_edit: Edit a BGP session
  • fdb_lookup: Lookup forwarding database (FDB) entries
  • nac_list: List network access control (802.1X / MAB) sessions across all devices
  • ospf_list: List OSPF instances
  • ospf_ports: List OSPF ports
  • vrf_list: List VRFs
  • ping: Ping the LibreNMS system
  • health_list: List health sensors
  • health_by_type: List health sensors by type
  • health_sensor_get: Get details for a health sensor
  • sensors_list: List sensors
  • switching_vlans: List all VLANs from LibreNMS.
  • switching_links: List all links from LibreNMS.
  • system_info: Get system info from LibreNMS.

  • Flexible filtering and search for all major resources (devices, ports, alerts, logs, inventory, etc.)

📄 Pagination & Limit Support

To prevent overloading LLM contexts when querying large LibreNMS production instances, all list, search, and log tools support pagination.

Key Features

  • Sensible Defaults: All list tools default to returning 100 results per page.
  • Unified Parameters:
  • limit: The maximum number of results to return (defaults to 100, minimum 1).
  • offset (or start for log tools): The number of results to skip.
  • Pagination Metadata: Every paginated response includes metadata fields:
  • limit: The active limit.
  • offset (or start): The active offset.
  • count: The number of items returned in the current page.
  • total: The total number of items available (for log tools, this is provided if returned by the LibreNMS API).

🚨 Error Responses

Every tool that returns JSON reports a failure in LibreNMS's own error shape,
whether the error came from LibreNMS, from a check in this server, or from an
exception such as a timeout:```json
{"status": "error", "message": "Device typo does not exist"}


Check `status == "error"`. Up to 1.11.3, exceptions were returned as
`{"error": "..."}`; clients that looked for an `error` key need updating.

## 🔒 Security & Safety Features

### Read-Only Mode

The server supports a read-only mode that disables all write operations for safe monitoring:```env
READ_ONLY_MODE=true

Tag-Based Tool Filtering

You can disable specific categories of tools by setting disabled tags:```env
DISABLED_TAGS=alert,alert-rules,alert-templates,bills


A tool is hidden when any of its tags is disabled, and some tools carry more
than one category tag: for example, `port_graph` is tagged `graphs` and `ports`,
and `ospf_list` is tagged `routing` and `ospf`, so `DISABLED_TAGS=ports` also
hides `port_graph`. Alerting is split into three tags: `alert` (current alerts:
list, acknowledge, unmute), `alert-rules` and `alert-templates`; disable all
three to hide every alerting tool.

Besides the categories, `read-only` marks the tools that stay available in
read-only mode. The `admin` and `global-read` tags follow the permission groups
older LibreNMS releases used for their API routes (`can:admin`,
`can:global-read`). Current LibreNMS checks permissions per object instead, so
treat these two as broad categories rather than an exact match of what your
LibreNMS user may do.

### Tool Search for Large Toolsets

FastMCP tool search can reduce prompt size for servers with many tools.
When enabled, `list_tools` returns two synthetic tools:

- `search_tools`: Finds matching tools and returns their full schemas
- `call_tool`: Executes any discovered tool by name

Enable it with:```env
TOOL_SEARCH_ENABLED=true
TOOL_SEARCH_STRATEGY=bm25    # bm25 or regex
TOOL_SEARCH_MAX_RESULTS=5    # optional, default is 5

bm25 supports natural language queries, while regex uses a regex pattern input for deterministic matching.

Tool search respects existing visibility controls (read-only mode and disabled tags).

Rate Limiting

The server supports rate limiting to control API usage and prevent abuse. If enabled, requests are limited per client using a sliding window algorithm.

Enable rate limiting by setting the following environment variables in your .env file:```env
RATE_LIMIT_ENABLED=true
RATE_LIMIT_MAX_REQUESTS=100 # Maximum requests allowed per window
RATE_LIMIT_WINDOW_MINUTES=1 # Window size in minutes


If `RATE_LIMIT_ENABLED` is set to `true`, the server will apply rate limiting middleware. Adjust `RATE_LIMIT_MAX_REQUESTS` and `RATE_LIMIT_WINDOW_MINUTES` as needed for your environment.

### Sentry Error Tracking & Monitoring (Optional)

The server optionally supports **Sentry** for error tracking, performance monitoring, and debugging. Sentry integration is completely optional and only initialized if configured.

#### Installation

To enable Sentry monitoring, install the optional dependency:```sh
# Using UV (recommended)
uv sync --extra sentry

Configuration

Enable Sentry by setting the SENTRY_DSN environment variable in your .env file:```env

Required: Sentry DSN for your project

SENTRY_DSN=https://your-key@o12345.ingest.us.sentry.io/6789

Optional: Performance monitoring sample rate (0.0-1.0, default: 1.0)

SENTRY_TRACES_SAMPLE_RATE=1.0

Optional: Include personally identifiable information (default: false).

When true, tool inputs and outputs (device configs, SNMP credentials) are sent to Sentry.

SENTRY_SEND_DEFAULT_PII=false

Optional: Environment name (e.g., "production", "staging")

SENTRY_ENVIRONMENT=production

Optional: Release version (auto-detected from package if not set)

SENTRY_RELEASE=1.2.2

Optional: Profiling - continuous profiling sample rate (0.0-1.0, default: 1.0)

SENTRY_PROFILE_SESSION_SAMPLE_RATE=1.0

Optional: Profiling - lifecycle mode for profiling (default: "trace")

Options: "all", "continuation", "trace"

SENTRY_PROFILE_LIFECYCLE=trace

Optional: Enable log capture as breadcrumbs and events (default: true)

SENTRY_ENABLE_LOGS=true


#### Features

When enabled, Sentry automatically captures:

- **Exceptions & Errors**: All unhandled exceptions with full context
- **Performance Metrics**: Request/response times and traces
- **MCP Integration**: Detailed MCP server activity and interactions
- **Logs & Breadcrumbs**: Application logs and event trails for debugging
- **Context Data**: Environment, client info, and request parameters

#### Getting a Sentry DSN

1. Create a free account at sentry.io
2. Create a new Python project
3. Copy your DSN from the project settings
4. Set it in your `.env` file

#### Disabling Sentry

Sentry is completely optional. If you don't set `SENTRY_DSN`, the server will run normally without any Sentry integration, and no monitoring data will be collected.

### SSL/TLS Configuration

The server supports SSL certificate verification and custom timeout settings:```env
LIBRENMS_VERIFY_SSL=true    # Enable SSL certificate verification
LIBRENMS_TIMEOUT=30         # Connection timeout in seconds

Transport Configuration

The server supports multiple transport mechanisms for the MCP protocol. MCP_TRANSPORT is case-insensitive, streamable-http is accepted as an alias for http, and any other value stops the server at startup with an error rather than silently falling back to STDIO:

STDIO Transport (Default)

The default transport uses standard input/output for communication. This is ideal for local usage and integration with tools that communicate via stdin/stdout:```env
MCP_TRANSPORT=stdio


#### HTTP SSE Transport (Server-Sent Events)

For network-based deployments, you can use HTTP with Server-Sent Events. This allows the MCP server to be accessed over HTTP with real-time streaming:```env
MCP_TRANSPORT=sse
MCP_HTTP_HOST=127.0.0.1        # Localhost
MCP_HTTP_PORT=8000           # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token  # Optional authentication token

When using SSE transport with a bearer token, clients must include the token in their requests:```bash
curl -H "Authorization: Bearer your-secret-token" http://localhost:8000/sse


#### HTTP Streamable Transport

The HTTP Streamable transport provides HTTP-based communication with request/response streaming. This is ideal for web integrations and tools that need HTTP endpoints:```env
MCP_TRANSPORT=http
MCP_HTTP_HOST=127.0.0.1        # Localhost
MCP_HTTP_PORT=8000           # Port to listen on
MCP_HTTP_BEARER_TOKEN=your-secret-token  # Optional authentication token

When using streamable transport with a bearer token:```sh
curl -H "Authorization: Bearer your-secret-token" \
-H "Accept: application/json, text/event-stream" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
http://localhost:8000/mcp


**Note**: The HTTP transport requires proper JSON-RPC formatting with `jsonrpc` and `id` fields. The server may also require session initialization for some operations.

#### Health Endpoint

Both HTTP transports (`sse` and `http`) serve `GET /health`, which answers `200 ok`
when the server is handling requests. It needs no bearer token and does not
contact LibreNMS, so a LibreNMS outage does not mark the MCP server unhealthy.
The Docker image's `HEALTHCHECK` uses it:```sh
curl http://localhost:8000/health

For more information on FastMCP transports, see the FastMCP documentation.

🤝 Contributing

Contributions are welcome. See CONTRIBUTING.md for the dev setup, checks and commit message format, and use the issue templates for bugs and feature requests.

Found a security problem? Please report it privately as described in SECURITY.md.

📜 License

MIT License - see LICENSE for details.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Librenms MCP 怎么安装?

在客户端按下面的安装命令接入:pip install librenms-mcp。装完在客户端配置里引用同一个包或端点。

Librenms MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Librenms MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Librenms MCP 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Librenms MCP 能提供哪些能力?

资料显示能力标签包括 网络监控、Python、自动化管理、API集成。具体工具清单以官方文档为准。

Librenms MCP 需要什么运行环境?

运行时为 Python;属于远程端点,不需要在本地装运行时。

Librenms MCP 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为SSE · 服务端推送。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。