{
"mcpServers": {
"mcp-lcu-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 348 days ago. 9 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Mcp_lcu_server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The Model Context Protocol (MCP) Linux Common Utility (LCU) Server is a Python-based server that provides access to various Linux system operations and information through the Model Context Protocol.
Clone the repository:
git clone https://github.com/yourusername/mcp_lcu_server.git
cd mcp_lcu_server
Install the package:
uv venv
source .venv/bin/activate
python -m build
The server can be configured using a YAML configuration file. By default, it looks for the configuration file in the following locations:
./config.yaml./config/config.yaml/etc/mcp-lcu-server/config.yaml~/.config/mcp-lcu-server/config.yamlYou can also specify a custom configuration file path using the --config command-line option.
server:
name: mcp-lcu-server
transport: both # stdio, sse, or both
port: 8000
host: 127.0.0.1
monitoring:
enabled: true
interval: 30 # seconds
metrics:
- cpu
- memory
- disk
- network
filesystem:
allowed_paths:
- /
max_file_size: 10485760 # 10MB
network:
allow_downloads: true
allow_uploads: true
max_download_size: 104857600 # 100MB
max_upload_size: 10485760 # 10MB
allowed_domains:
- "*" # Allow all domains
process:
allow_kill: false
allowed_users: []
logs:
# Custom log paths (optional)
paths:
# syslog: /var/log/syslog
# auth: /var/log/auth.log
max_entries: 1000 # Maximum entries to return
You can start the server using the command-line interface:
mcp-lcu-server [OPTIONS]
Available options:
--config, -c: Path to the configuration file--transport, -t: Transport type (stdio, sse, or both)--port, -p: Port for SSE transport--host, -h: Host for SSE transport--debug, -d: Enable debug loggingThe server supports the following transport types:
stdio: Standard input/output transportsse: Server-Sent Events transportStart the server with stdio transport:
mcp-lcu-server --transport stdio
Start the server with SSE transport on port 8000:
mcp-lcu-server --transport sse --port 8000
Start the server with both transports:
mcp-lcu-server --transport both
The server provides various tools for interacting with the Linux system:
get_cpu_info: Get detailed CPU informationget_cpu_usage: Get CPU usage percentageget_load_average: Get system load averageanalyze_cpu_performance: Analyze CPU performanceget_memory_info: Get detailed memory informationget_memory_usage: Get memory usage