Linux MCP server
Commit Nov 13, 2026Provides real-time Linux system monitoring and diagnostics including CPU, memory, disk, network, processes, and Docker metrics via MCP tools.
Also known as Mohabdo21/linux-mcp, linux-mcp
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.3.0
- Last commit
- Nov 13, 2026
- License
- MIT
What is Linux MCP?
Linux provides real-time Linux system monitoring and diagnostics including CPU, memory, disk, network, processes, and Docker metrics via MCP tools.
Summary generated from the project's README
About Linux MCP server
Linux MCP provides real-time monitoring and diagnostic capabilities for Linux systems through the Model Context Protocol. It allows developers and system administrators to inspect hardware, software, and network metrics using an AI client. The server operates over STDIO transport and can be integrated into environments like Claude Desktop, Claude Code, OpenCode, or Codex. It requires a Linux environment and can be installed via the MCP Registry, pre-built binaries, or by building from source using Go.
The server includes 65 tools and 19 resources that cover a wide range of system data. Users can monitor CPU usage, memory and swap consumption, disk partition details, and network interface statistics. It also provides deep visibility into running processes, systemd units, and Docker container metrics. Security features include auditing for failed logins, firewall status, and SUID files, while hardware tools report on GPU information and PCI or USB bus devices.
What you can do with it
- 1Analyze system performanceRequest a comprehensive overview of the current system state including load averages and uptime.
- 2Debug Docker environmentsCheck the status and resource usage of running containers and images.
- 3Audit system securityIdentify potential security risks by checking failed login attempts and firewall configurations.
- 4Inspect low-level kernel dataPerform deep diagnostics by looking into interrupts and filesystem statistics via the proc directory.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemohabdo21/linux-mcp is public and reachablegithub.com/mohabdo21/linux-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-05github.com/mohabdo21/linux-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHublinux-mcp - Linux MCP Server
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.
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
- /proc diagnostics - deep /proc inspection: interrupts, softirqs, vmstat, diskstats, filesystems, kernel version, slabinfo
- Man pages - system manual pages for any installed command
- Snapshot - comprehensive system overview in a single call
- MCP Resources - system data also accessible as readable resources
Prerequisites
- Go 1.27+ (to build from source)
- Linux (the server targets Linux; some tools use Linux-specific paths)
- Docker (optional - only needed for Docker tools)
Installation
Via MCP Registry
Discover the server on the MCP Registry and install via your MCP client (VS Code one-click install, or manual config).
Download pre-built binary
Download the latest binary from the GitHub Releases page:
curl -LO https://github.com/Mohabdo21/linux-mcp/releases/latest/download/linux-mcp
chmod +x linux-mcp
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.
Integration
Add the following to your OpenCode configuration:
{
"mcp": {
"linux-mcp": {
"type": "local",
"command": ["/path/to/linux-mcp"],
"enabled": true
}
}
}
Add the server via the CLI:
claude mcp add linux-mcp -- /path/to/linux-mcp
To scope it to all your projects instead of just the current one:
claude mcp add linux-mcp --scope user -- /path/to/linux-mcp
Or create a .mcp.json file in your project root for team-shared configuration:
{
"mcpServers": {
"linux-mcp": {
"type": "stdio",
"command": "/path/to/linux-mcp"
}
}
}
Verify the connection inside a Claude Code session with /mcp.
Add the server via the CLI:
codex mcp add linux-mcp -- /path/to/linux-mcp
Or add it manually to ~/.codex/config.toml (or .codex/config.toml for project-scoped config):
[mcp_servers.linux-mcp]
command = "/path/to/linux-mcp"
Verify the connection with codex mcp list.
Tools and resources
65 tools and 19 resources covering system, CPU, memory, disk, network, processes, Docker, security, packages, hardware, and more.
Full tool and resource reference
Configuration
The server can be configured via a JSON file loaded from ~/.config/linux-mcp/config.json or the LINUX_MCP_CONFIG environment variable.
{
"log_level": "info",
"timeouts": {
"get_system_snapshot": "60s",
"ping_host": "5s"
},
"disabled": []
}
| Field | Description |
|---|---|
log_level |
One of debug, info, warn, error (default: info) |
timeouts |
Per-tool timeout overrides as Go duration strings |
disabled |
Tool names to disable, including their resource and aggregate collector paths |
Invalid configuration prevents startup. The server also handles SIGHUP to reload the configuration file at runtime without restarting; a failed reload retains the last valid configuration. Disabled collectors are skipped by aggregate tools and reported in their errors.
Docker diagnostic responses omit environment values and raw command arguments, including image-history commands. Other diagnostic content, such as logs and labels, can still contain sensitive data; grant access only to trusted clients.
MCP Registry
Published on the MCP Registry as io.github.Mohabdo21/linux-mcp.
License
Dependencies
- modelcontextprotocol/go-sdk - MCP SDK for Go
- shirou/gopsutil/v4 - System metrics (CPU, memory, disk, network, processes, sensors)
- docker/go-sdk - Docker Engine API client
- moby/moby/client - Docker client library
- ip-api.com - Free IP geolocation API (used by
get_ip_info)
Linux MCP questions
What system information can I monitor?
You can monitor hostname, OS, kernel, architecture, uptime, load averages, CPU usage, memory, disk partitions, network stats, and running processes.
Does this server support Docker monitoring?
Yes, it provides tools for containers, images, networks, volumes, disk usage, system info, and container stats.