dashynms/mcp
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
DashyNMS MCP Server
개요
Ask Claude about your LibreNMS network. For Claude Desktop, Claude Code and any other MCP client. Website · Container image · Release notes · Roadmap "What's alerting right now?" "How is the core switch doing?" "What changed on this firewall since yesterday?" DashyNMS MCP lets an AI assistant answer questions like these from your own LibreNMS server, with the evidence beside every answer, and without being able to change a thing. It's a Model Context Protocol server, built on the same LibreNMS, Unimus and Graylog code as DashyNMS desktop and DashyNMS Mobile. Its features match DashyNMS desktop and mobile 1.1, and later versions follow theirs; the milestones show what's next. By part of a name, an IP address, or a MAC address, or list devices by status, device group or location: "which devices are down at the north site?". A MAC is looked up in LibreNMS's ARP tables, so you find the router or switch that saw it.
README
원문 README의 일부입니다. 원문 보기.
DashyNMS MCP
Ask Claude about your LibreNMS network. For Claude Desktop, Claude Code and any other MCP client.
Website · Container image · Release notes · Roadmap
“What’s alerting right now?” “How is the core switch doing?” “What changed on this firewall since yesterday?” DashyNMS MCP lets an AI assistant answer questions like these from your own LibreNMS server, with the evidence beside every answer, and without being able to change a thing.
It’s a Model Context Protocol server, built on the same LibreNMS, Unimus and Graylog code as DashyNMS desktop and DashyNMS Mobile.
Its features match DashyNMS desktop and mobile 1.1, and later versions follow theirs; the milestones show what’s next.
What you can ask
Find anything
By part of a name, an IP address, or a MAC address, or list devices by status, device group or location: “which devices are down at the north site?”. A MAC is looked up in LibreNMS’s ARP tables, so you find the router or switch that saw it. (find_device, list_groups_and_locations)
Is it OK?
One answer per device: up or down, uptime, maintenance, open alerts, CPU, memory, the fullest storage, and the ports that are down or counting errors. (device_health)
What’s on that port?
State, speed, VLANs, traffic, errors, its description, and the neighbour LibreNMS sees on it over LLDP or CDP. (port_status)
Everything else about a device
Its inventory with models and serials, VLANs with their tagged and untagged ports, the MAC and ARP tables, PoE budget, wireless, BGP and OSPF, availability over the last day to year, and its own IP addresses. Ask for just the parts you need. (device_details)
Is anything running hot?
Temperatures, fans, optical power, voltages and more, for one device or across the network, worst first, judged the same way as DashyNMS’s Health tab. (device_sensors, health_overview)
What’s it connected to?
Every LLDP and CDP neighbour of a device, including ones that report it when it doesn’t report them back. (device_neighbours)
Where is this plugged in?
설치
docker run -i --rm --env-file C:\\path\\to\\dashynms.env ghcr.io/dashynms/mcp:latest설정
{
"mcpServers": {
"dashynms": {
"command": "docker",
"args": ["run", "-i", "--rm", "--env-file", "C:\\path\\to\\dashynms.env", "ghcr.io/dashynms/mcp:latest"]
}
}
}