System Information 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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_system_infoB | Get basic information about the host system (OS, memory, arch) |
| get_current_timeA | Get the current localized time on the host system |
| get_disk_usageB | Get disk space information for all drives |
| get_cpu_loadB | Get current CPU load and average information |
| get_network_interfacesB | Get details about all network interfaces |
| get_user_pathsB | Get absolute paths to common user folders (Home, Documents, Downloads) |
| list_directoryC | List contents of a directory with file sizes and dates |
| move_filesC | Move or rename files/directories |
| search_filesC | Search for files in a directory matching a pattern |
| delete_filesC | Delete files or directories (permanent removal) |
| find_large_filesC | Find files larger than a specified size (in MB) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| system_health_check | System Health Check |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Static OS Information |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose targeting specific system resources or operations. There is no overlap between tools like get_cpu_load (CPU metrics), get_disk_usage (storage), list_directory (file listing), and delete_files (file deletion). The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tools follow a consistent verb_noun naming pattern using snake_case, such as get_cpu_load, list_directory, and delete_files. This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or convention across the 11 tools.
With 11 tools, the count is well-scoped for a system information server, covering key areas like CPU, disk, network, files, and time without being overwhelming. Each tool earns its place by addressing a distinct aspect of system monitoring and file management, avoiding redundancy.
The tool set provides comprehensive coverage for system information retrieval and basic file operations, including getters for CPU, disk, network, and system info, plus file actions like list, search, move, and delete. A minor gap is the lack of file creation or editing tools, but agents can work around this with existing tools for most workflows.