get_cpu_infoLABSCO SUMMARY
The machine's own numbers, without a second terminal.
It answers the questions that usually send you to top and df in another window, which means the assistant reasoning about a slowdown is looking at the same figures you would. Temperature is the one tool whose answer depends on hardware — it reports sensors when the machine exposes them.
What it is
A read-only window onto the machine the server runs on. Each tool answers one question about current state, with caching in front so repeated asks do not re-measure, and it runs the same way on Windows, macOS and Linux.
What you get
- CPU usage, core counts, frequency and load average
- Virtual and swap memory statistics
- Disk usage across every mount, or for one path you name
- Network interface details and I/O counters
- The running process list, sorted and filtered the way you ask
- Boot time and uptime
- Temperature sensors and fan speeds, on hardware that reports them
Requirements
uvx on your PATH — the server runs as uvx mcp-system-info, with no account or key involved.
Setup effort
One command — uvx mcp-system-info
USE CASES
01
Working out why the machine feels slow
Take CPU and memory together, then pull the process list sorted by whichever of the two is under pressure, so the answer names a process rather than a symptom.
02
Finding out what filled the disk
Read usage across every mount, or narrow to one path, and get back the figures that say which volume is actually the problem.
03
Checking a box before a long job
Confirm there is headroom in cores, memory and disk before starting something that will run for hours, and see how long the machine has been up since its last restart.
04
Watching thermals during heavy work
Read sensor temperatures and fan speeds alongside CPU load, which is the pairing that tells you whether a slowdown is throttling rather than contention.
05
Checking the network side of a stall
Interface details and I/O counters come back together, so a transfer that has stopped moving can be separated from a link that is down.
7 tools
Listed in project docs. Your client may show a different list.
get_memory_infoget_disk_infoget_network_infoget_process_listget_system_uptimeget_temperature_infoBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
uvx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-system-infoMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"system-info": {
"command": "uvx",
"args": [
"mcp-system-info"
],
"env": {
"SYSINFO_CACHE_TTL": "10",
"SYSINFO_LOG_LEVEL": "INFO"
}
}
}
}Claude Desktop — local build
CLAUDE DESKTOP — LOCAL BUILD · TERMINAL
git clone https://github.com/dknell/mcp-system-info.git
cd mcp-system-info
uv syncCLAUDE DESKTOP — LOCAL BUILD · JSON
{
"mcpServers": {
"system-info": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_MCP_SYSTEM_INFO>",
"run",
"mcp-system-info"
],
"env": {
"SYSINFO_TRANSPORT": "stdio",
"SYSINFO_CACHE_TTL": "10",
"SYSINFO_LOG_LEVEL": "INFO"
}
}
}
}<YOUR_PATH_TO_MCP_SYSTEM_INFO> is the full path of your clone.
