mcp-system-monitor
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_resourcesA | Get current CPU, memory, and disk usage statistics |
| list_processesA | List running processes with CPU and memory usage, sorted by resource consumption |
| get_network_connectionsB | Get active network connections and listening ports |
| get_docker_statusA | Get status of Docker containers (if Docker is available) |
| get_system_logsA | Get recent system logs from journalctl (Linux only) |
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 5 tools
Each tool targets a distinct monitoring domain: system resources, network, processes, Docker, and logs. There is no overlap or ambiguity between the tools.
All tool names follow the same get_<object> pattern, using snake_case consistently. The naming is predictable and easy to navigate.
Five tools is a well-scoped size for a system monitoring server, covering the primary monitoring surfaces without unnecessary bloat.
The tool surface covers the main system monitoring areas: resources, network, processes, containers, and logs. Minor gaps like disk I/O statistics or service management exist, but the core monitoring workflows are well supported.