MCP Linux Common Utility Server

What is MCP Linux Common Utility Server?

The Model Context Protocol (MCP) Linux Common Utility (LCU) Server is a Python‑based server that exposes a wide range of Linux system operations — including CPU, memory, processes, filesystem, hardware, network, monitoring, and logs — as MCP tools and resources. It is built for developers and system administrators who want to interact with a Linux host programmatically through any MCP client.

How to use MCP Linux Common Utility Server?

Install the package from source (requires Python 3.10+ and a Linux OS). Start the server with the mcp-lcu-server command, choosing the transport type (stdio, sse, or both) and optionally a custom port/host. Behaviour such as allowed paths, process kill permissions, and monitoring intervals are set via a YAML configuration file (default locations: ./config.yaml, ./config/config.yaml, /etc/mcp-lcu-server/config.yaml, ~/.config/mcp-lcu-server/config.yaml).

Key features of MCP Linux Common Utility Server

• CPU, memory, and swap monitoring tools
• Process listing, search, and analysis
• Filesystem CRUD and search operations
• Network connectivity, stats, and file transfers
• System monitoring, health checks, and uptime
• Log access from journal, syslog, dmesg, and services

Use cases of MCP Linux Common Utility Server

• Analyze CPU and memory performance on a remote Linux server
• List processes and get top CPU/memory consumers
• Read, write, or delete files on the filesystem via an AI agent
• Monitor system health and resource usage over time
• Diagnose network issues with ping, traceroute, and interface stats

FAQ from MCP Linux Common Utility Server

What dependencies or runtime are required?

Python 3.10 or higher and a Linux operating system.

What transports are supported?

The server supports stdio, SSE (Server‑Sent Events), or both simultaneously.

Can I restrict filesystem or network access?

Yes. In the YAML config you can set allowed_paths, max_file_size, allowed_domains, and disable uploads/downloads.

Is process killing allowed by default?

No. The process.allow_kill option is false by default; it must be explicitly enabled in the configuration.

How do I disable the command execution feature?

Set command.enabled: false in your configuration file. You can also restrict allowed/blocked commands and disable sudo access separately.