Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP System Info Server show me current CPU and memory usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: MCP System Info Server
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
Clone the repository:
git clone https://github.com/allenbijo/mcp-sysinfo.gitAdd the MCP server to your client:
On Claude
{
"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.
Endpoint | Description |
| Returns system details |
This project is licensed under the MIT License.
Allen Bijo - GitHub
Get the current system information. Gives system information such as System, Node name, Release, Version, Machine, Processor CPU Information such as Processor, Physical Cores, Logical Cores Memory Information such as Total Memory, Available Memory, Used Memory, Memory Utilization Disk Information such as Total Disk Space, Used Disk Space, Free Disk Space, Disk Space Utilization
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.
Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
Heartbeat and tokens/sec monitoring for self-hosted LLM servers (Ollama etc.), with down alerts.
CPU telemetry & benchmarking, SHA-256 hashing, AES-256-GCM storage, AI video/image via Nova.
