MCP System Info Server
Provides real-time monitoring of NVIDIA GPU statistics, including utilization, temperature, and memory usage.
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 my current CPU, memory, and GPU 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.
MCP System Info Server
A lightweight MCP (Model Context Protocol) server that provides real-time system information including CPU, memory, disk, and GPU statistics.
Features
Category | Information Provided |
System | System name, node name, OS release/version, machine type, processor |
CPU | Processor name, physical/logical cores, frequency, usage percentage |
Memory | Total, available, used memory (GB), utilization percentage |
Disk | Total, used, free space (GB), utilization percentage |
GPU | Name, memory (total/used/free), utilization, temperature (NVIDIA only) |
Related MCP server: System Stats MCP Server
Prerequisites
Python 3.10+
uv - Fast Python package manager
Installation
# Clone or navigate to the project directory
cd mcp
# Install dependencies (handled automatically by uv)
uv syncScreenshots


Usage
Running Standalone
uv run sysinfo.pyTesting with MCP Inspector
uv run mcp dev sysinfo.pyClaude Desktop Configuration
Add this to your Claude Desktop configuration file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"sysinfo": {
"command": "uv",
"args": [
"--directory",
"PATH OF THE FOLDER",
"run",
"sysinfo.py"
]
}
}
}Available Tools
get_sysinfo
Returns comprehensive system information as a JSON object:
{
"system": {
"system_name": "Windows",
"node_name": "DESKTOP-XXX",
"os_release": "10",
"os_version": "10.0.19045",
"machine_type": "AMD64",
"processor": "Intel64 Family 6..."
},
"cpu": {
"processor_name": "Intel Core i7-10700K",
"physical_cores": 8,
"logical_cores": 16,
"cpu_frequency_mhz": 3800.0,
"cpu_usage_percent": 12.5
},
"memory": {
"total_gb": 32.0,
"available_gb": 18.5,
"used_gb": 13.5,
"utilization_percent": 42.2
},
"disk": {
"total_gb": 500.0,
"used_gb": 280.0,
"free_gb": 220.0,
"utilization_percent": 56.0
},
"gpu": [
{
"id": 0,
"name": "NVIDIA GeForce RTX 3080",
"memory_total_mb": 10240.0,
"memory_used_mb": 2048.0,
"memory_free_mb": 8192.0,
"gpu_utilization_percent": 15.0,
"temperature_c": 45
}
]
}Dependencies
mcp[cli] - MCP SDK with CLI support
psutil - Cross-platform system information
GPUtil - NVIDIA GPU information
py-cpuinfo - Detailed CPU information
Available Tools
1 toolget_sysinfoB
Get comprehensive system information.
Returns detailed information about the system including:
- System: OS name, version, machine type
- CPU: Processor name, cores, frequency, usage
- Memory: Total, available, used memory and utilization
- Disk: Total, used, free disk space and utilization
- GPU: NVIDIA GPU details if available (name, memory, utilization, temperature)
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_sysinfo' has a clearly defined and distinct purpose of retrieving comprehensive system information.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_sysinfo' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and scope. For a system info server, one tool might be insufficient for covering potential needs like monitoring specific components or historical data, making it feel thin and under-scoped.
The tool provides comprehensive system information in one call, but there are significant gaps for a system info domain. Missing operations include monitoring changes over time, querying specific subsystems individually, or performing actions like alerts or logs, which limits agent workflows and could lead to failures in dynamic scenarios.
Maintenance
Related MCP Connectors
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
Live health and AI-readable metadata of invokera.com. Demo of an Invokera-hosted MCP server.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Related MCP Servers
- AlicenseAqualityDmaintenanceA lightweight server that provides real-time system information including CPU, memory, disk, and GPU statistics for monitoring and diagnostic purposes.1MIT
- FlicenseNot gradedqualityCmaintenanceProvides real-time Linux system monitoring for CPU load, memory usage, disk space, and process activity. This server enables users to retrieve comprehensive performance metrics and resource utilization data through a standardized interface.-
- FlicenseNot gradedqualityDmaintenanceA Windows-based MCP server that provides real-time hardware telemetry and system stats including CPU, RAM, disk, and battery information to GitHub Copilot. It enables users to monitor performance and retrieve detailed system specifications through natural language commands.-
- AlicenseNot gradedqualityCmaintenanceA real-time system diagnostics MCP server that gives AI agents live access to CPU, RAM, disk, network, processes, and hardware health metrics, with zero cloud dependency.7Apache 2.0