Linux MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_journal_logsC | Get systemd journal logs. |
| read_log_fileB | Read a specific log file. |
| get_network_interfacesA | Get detailed information about network interfaces including address and traffic statistics. |
| get_network_connectionsB | Get detailed information about active network connections. |
| get_listening_portsB | Get details on listening port, protocols, and services. |
| list_processesB | List running processes |
| get_process_infoA | Get information about a specific process. |
| list_servicesB | List all systemd services. |
| get_service_statusA | Get detailed status of a specific systemd service. |
| get_service_logsB | Get recent logs for a specific systemd service. |
| list_block_devicesA | List block devices on the system |
| list_directoriesA | List directories under a specified path with various sorting options. |
| list_filesB | List files under a specified path with various sorting options. |
| read_fileB | Read the contents of a text file up to a safe size limit. |
| get_system_informationA | Get basic system information such as operating system, distribution, kernel version, uptime, and last boot time. |
| get_cpu_informationC | Get CPU information. |
| get_memory_informationB | Get detailed memory including physical and swap. |
| get_disk_usageA | Get detailed disk space information including size, mount points, and utilization. |
| get_hardware_informationB | Get hardware information such as CPU details, PCI devices, USB devices, and hardware information from DMI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.