MCP System Info Server
# MCP System Info Server
## Overview
The **MCP System Info Server** is a lightweight and efficient server that provides real-time system information. It retrieves various hardware and system details, including CPU, memory, disk, and GPU statistics, making it useful for monitoring and diagnostic purposes.
## Features
- **System Information**
- System Name
- Node Name
- OS Release
- OS Version
- Machine Type
- Processor
- **CPU Information**
- Processor Name
- Physical Cores
- Logical Cores
- **Memory Information**
- Total Memory
- Available Memory
- Used Memory
- Memory Utilization
- **Disk Information**
- Total Disk Space
- Used Disk Space
- Free Disk Space
- Disk Space Utilization
## Installation
1. Clone the repository:
```sh
git clone https://github.com/allenbijo/mcp-sysinfo.git
```
## Usage
Add the MCP server to your client:
On Claude
```sh
{
"mcpServers": {
"sysinfo": {
"command": "uv",
"args": [
"--directory",
"D:\\WorksOfGreatness\\mcp-sysinfo",
"run",
"sysinfo.py"
]
}
}
}
```
The server will start and listen for incoming requests, providing real-time system information.
## API Endpoints
| Endpoint | Description |
|--------------|--------------------------|
|`/get_sysinfo`| Returns system details |
## License
This project is licensed under the MIT License.
## Author
Allen Bijo - [GitHub](https://github.com/allenbijo)
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'get_sysinfo' has a clear and distinct purpose of retrieving comprehensive system information, making it impossible for an agent to misselect among tools.
Since there is only one tool, it inherently follows a consistent naming pattern. The name 'get_sysinfo' uses a verb_noun format that is clear and predictable, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'MCP System Info Server', which suggests a broader scope for system information retrieval. While 'get_sysinfo' provides comprehensive data, the lack of additional tools (e.g., for specific components like CPU, memory, or disk details) makes the set feel thin and underdeveloped for the domain.
The tool 'get_sysinfo' covers a wide range of system information in one call, but the server's purpose implies potential for more granular operations. There are significant gaps, such as no tools for querying specific system metrics separately (e.g., get_cpu_info, get_memory_usage) or performing actions like monitoring changes, which limits agent flexibility and could lead to inefficiencies.