A Linux system monitoring server built on the Model Context Protocol (MCP). Provides real-time system information - CPU, memory, disk, network, processes, Docker, and more - via MCP tools over STDIO transport.
Linux MCP server for real-time system monitoring - CPU, memory, disk, network, processes, Docker.
2026-11-12
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Features
System - hostname, OS, kernel, architecture, uptime, load averages
CPU - usage, model, frequency, core counts, temperature sensors
Memory - RAM and swap usage with percentages
Disk - per-partition usage, inodes, mount options, largest files, block devices
Network - interface stats, active connections, listening ports, DNS, ping, IP geolocation & ASN lookup
Processes - running processes sorted by CPU or memory, open file descriptors per process
Docker - containers, images, networks, volumes, disk usage, system info, and container stats
Services & automation - systemd units, service status, user timers, crontab, system cron jobs
Security - active user sessions, failed login detection, SELinux/AppArmor status, firewall/SSH/SUID/world-writable audit with security score
Packages - installed packages and available updates (pacman, dpkg, rpm/dnf, apk)
Hardware - GPU info, PCI/USB bus devices, power/battery analytics
Desktop session - Wayland/X11 protocol, DE identifiers, runtime config
Storage health - RAID status, logrotate configuration, time synchronization, SMART disk health, per-device I/O metrics
System health - comprehensive health assessment with memory, disk, load, and systemd checks
A fully static build (no libc dependency) is also available as linux-mcp_static.
Via go install
go install github.com/Mohabdo21/linux-mcp@latest
The binary is placed in $GOPATH/bin/ (typically ~/go/bin/).
Build from source
git clone https://github.com/Mohabdo21/linux-mcp.git
cd linux-mcp
make build
The binary is placed at bin/linux-mcp.
For a fully static binary (no libc dependency):
make build-static
Usage
The server communicates over STDIO transport, following the MCP standard. It is designed to be launched by an MCP client (e.g., Claude Desktop, Claude Code, Codex, OpenCode, or any MCP host).
Running directly
./bin/linux-mcp
This starts the server and listens for MCP requests on STDIN/STDOUT.
