Linux MCP Server
Provides read-only tools for Linux system administration, diagnostics, and troubleshooting, including capabilities to inspect system information, services, processes, logs, networking, and storage.
Specifically optimized for Red Hat Enterprise Linux (RHEL) systems, allowing for remote diagnostics and system administration on RHEL-based systems with a focus on systemd-managed environments.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Linux MCP Server Check the CPU usage and list any failed services on web-server-01"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: Linux Diagnostics MCP Server
Installation and Usage
For detailed instructions on setting up and using the Linux MCP Server, please refer to our documentation.
Available Tools
23 toolsget_cpu_informationGet CPU informationCRead-only
Get CPU information.
Inputs: host (required). Returns: Parsed CPU information.
get_disk_usageGet disk usageARead-only
Get detailed disk space information including size, mount points, and utilization.
Inputs: host (required). Returns: Disk usage information from findmnt --df --json.
get_hardware_informationGet hardware informationBRead-only
Get hardware information such as CPU details, PCI devices, USB devices, and hardware information from DMI.
Inputs: host (required). Returns: object
get_journal_logsGet journal logsCRead-only
Get systemd journal logs.
Inputs: host (required), unit, since, priority, +3 more. Returns: path, unit, entries, lines_count
get_listening_portsGet listening portsBRead-only
Get details on listening port, protocols, and services.
Inputs: host (required). Returns: result
get_memory_informationGet memory informationBRead-only
Get detailed memory including physical and swap.
Inputs: host (required). Returns: Combined memory and swap information.
get_network_connectionsGet network connectionsBRead-only
Get detailed information about active network connections.
Inputs: host (required). Returns: result
get_network_interfacesGet network interfacesBRead-only
Get detailed information about network interfaces including address and traffic statistics.
Inputs: host (required). Returns: result
get_process_infoProcess detailsBRead-only
Get information about a specific process.
Inputs: pid (required), host (required). Returns: result
get_service_logsGet service logsBRead-only
Get recent logs for a specific systemd service.
Inputs: host (required), service_name (required), lines. Returns: result
get_service_statusGet service statusARead-only
Get detailed status of a specific systemd service.
Inputs: host (required), service_name (required). Returns: result
get_system_informationGet system informationARead-only
Get basic system information, including operating system, distribution, kernel version, uptime, last boot time, PCP installation and service status, and historical PCP time ranges.
Inputs: host (required). Returns: Parsed system information.
list_block_devicesList block devicesCRead-only
List block devices on the system
Inputs: host (required). Returns: total, blockdevices
list_directoriesList directoriesCRead-only
List directories under a specified path with various sorting options.
Inputs: host (required), path (required), sort, top_n, +1 more. Returns: nodes, total
list_filesList filesCRead-only
List files under a specified path with various sorting options.
Inputs: host (required), path (required), sort, top_n, +1 more. Returns: nodes, total
list_processesList processesCRead-only
List running processes
Inputs: host (required). Returns: result
list_servicesList servicesARead-only
List all systemd services.
Inputs: host (required). Returns: result
pcp_guideRead the PCP metrics guideARead-only
Returns the PCP metrics guide: a catalog of the metric names recorded on a typical Linux system, and how to read the values the other PCP tools return. Read it before investigating performance with PCP, and take metric names from it rather than from memory.
Inputs: host (required). Returns: result
pcp_list_metricsList available PCP metricsARead-only
Browses the PCP metric namespace. Lists the metrics under 'prefix' with their descriptions, collapsing any large sub-namespace to one line giving its name and how many metrics it holds; call again with that name as the prefix to see inside it. Only metrics this system's pmlogger records are listed, so everything listed can be passed to pcp_query_metrics. The pcp_guide tool already names the commonly needed metrics, so reach for this when you need a subsystem the guide does not cover. Use only if get_system_information() indicates PCP is available.
Inputs: host (required), prefix. Returns: result
pcp_performance_summaryGet PCP performance summaryARead-only
Produces a condensed snapshot of CPU, memory, disk, network, and process information using pcp xsos. Can summarize the live system or a particular time in the past. Use only if get_system_information() indicates PCP is available.
Inputs: host (required), timestamp. Returns: result
pcp_query_metricsQuery PCP historical metricsARead-only
Retrieves historical metric data from PCP archives as JSON samples. When start_time, end_time, or interval is omitted, reasonable defaults are chosen, targeting one hour or about 20 samples. Call pcp_guide first for the metric catalog and how to read the values; do not guess metric names. Use only if get_system_information() indicates PCP is available.
Inputs: host (required), metrics (required), end_time, interval, +1 more. Returns: result
read_fileRead fileBRead-only
Read the contents of a text file up to a safe size limit.
Inputs: host (required), path (required). Returns: result
read_log_fileRead log fileCRead-only
Read a specific log file.
Inputs: host (required), log_path (required), last_lines, first_lines. Returns: path, unit, entries, lines_count
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 23 tools
Most tools have clearly distinct targets (network, disk, processes, services, files, PCP metrics). Minor overlap exists: get_hardware_information explicitly includes CPU details while get_cpu_information is separate, and get_service_logs / get_journal_logs / read_log_file all retrieve logs, though descriptions differentiate the sources.
All tools follow a strict snake_case verb_noun pattern (get_*, list_*, read_*), with a consistent pcp_* prefix grouping the PCP subsystem tools. No mixing of conventions or casing.
23 tools is on the heavier side but the domain (comprehensive Linux system diagnostics) legitimately spans many subsystems. Nearly every tool earns its place, though a few informational getters (CPU, memory, hardware, system) could plausibly be consolidated.
Broad read-oriented coverage across CPU, memory, disk, network, processes, services, logs, files, and PCP performance with sensible PCP gating. Gaps are limited to write/action operations (e.g. restart service, kill process, file search), which is acceptable if the server is intentionally read-only.
Maintenance
Related MCP Connectors
Linux server administration over OAuth MCP: shell, Docker, systemd, files and monitoring.
Termalin's hosted MCP server. Claude, ChatGPT or any MCP client runs commands, moves files over SFTP, queries databases and reads server metrics and monitoring alerts on your servers, keylessly through Termalin Connectors: no SSH key is handed over and no inbound port is opened. Per-host command policy and an audit log. Needs a termal.in Pro or Team account (new accounts start with a 14-day Pro trial).
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables read-only Linux system diagnostics and troubleshooting on local and remote RHEL-based systems via SSH, including services, processes, logs, network, and storage analysis.20MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides read-only Linux system diagnostics tools for inspecting system information, processes, and log snapshots. It enables AI models to analyze Linux system health, troubleshoot issues, and review security through workflow prompts and HTTP transport with API key authentication.MIT
- AlicenseAqualityDmaintenanceMCP server for remote Linux/Unix server management via SSH, enabling command execution, system monitoring, file operations, and diagnostics through natural language.341MIT
- AlicenseNot gradedqualityDmaintenanceA secure SSH-based MCP server for diagnosing remote servers. It allows AI agents to execute read-only commands and read files automatically, while requiring user confirmation for write operations.MIT