Linux MCP Server
<!-- mcp-name: io.github.rhel-lightspeed/linux-mcp-server -->
[](https://github.com/rhel-lightspeed/linux-mcp-server/actions/workflows/ci.yml)
[](https://codecov.io/gh/rhel-lightspeed/linux-mcp-server)
[](https://pypi.org/project/linux-mcp-server)
[](https://rhel-lightspeed.github.io/linux-mcp-server/)
# Linux MCP Server
A Model Context Protocol (MCP) server for read-only Linux system administration, diagnostics, and troubleshooting on RHEL-based systems.
## Features
- **Read-Only Operations**: All tools are strictly read-only for safe diagnostics
- **Remote SSH Execution**: Execute commands on remote systems via SSH with key-based authentication
- **Multi-Host Management**: Connect to different remote hosts in the same session
- **Comprehensive Diagnostics**: System info, services, processes, logs, network, and storage
- **Configurable Log Access**: Control which log files can be accessed via environment variables
- **RHEL/systemd Focused**: Optimized for Red Hat Enterprise Linux systems
## Installation and Usage
For detailed instructions on setting up and using the Linux MCP Server, please refer to our official documentation:
- **[Installation Guide]**: Detailed steps for `pip`, `uv`, and container-based deployments.
- **[Usage Guide]**: Information on running the server, configuring LLM clients, and troubleshooting.
- **[Cheatsheet]**: A reference for what prompts to use to invoke various tools.
[Installation Guide]: https://rhel-lightspeed.github.io/linux-mcp-server/install/
[Usage Guide]: https://rhel-lightspeed.github.io/linux-mcp-server/usage/
[Cheatsheet]: https://rhel-lightspeed.github.io/linux-mcp-server/cheatsheet/
TDQS
Scored across 19 tools
Each tool targets a distinct resource or action, with clear separation across logs, network, processes, services, files, and hardware. Minor overlap exists between get_hardware_information and get_cpu_information, and between get_journal_logs and get_service_logs, but descriptions mostly disambiguate them.
All tools follow a consistent snake_case verb_noun pattern, using get_, list_, or read_ appropriately. This makes the tool surface predictable and easy to navigate.
19 tools is slightly above the ideal 3-15 range, but the scope of a Linux system server justifies covering logs, network, processes, services, files, disks, and hardware. The count is manageable and each tool has a clear purpose.
The tool set covers most common read-only Linux administration tasks: system info, logs, processes, services, networking, files, and disk usage. It lacks write or lifecycle operations like creating files, managing processes, or restarting services, but the consistent read-only design suggests that is intentional.