get_system_infoLABSCO SUMMARY
Small surface, unusually complete plumbing.
One tool is the whole capability, so the reason to look at this is the transport work around it: it implements the Streamable HTTP spec on the root route with real session handling and keeps the older SSE route alive for clients that need it, with an nginx config in the README for putting it behind a proxy. That makes it as useful as a reference for wiring up a remote MCP server as it is for reading a load average.
What it is
A small Go server that answers one question: what is this machine doing right now. It returns CPU details — core count, model, load — and memory totals, used and available. The interesting part is the transport coverage: the same binary serves stdio for local clients, Streamable HTTP on / with Mcp-Session-Id session management and resumable streams, and the older HTTP+SSE protocol on /sse for clients that have not moved yet.
What you get
get_system_inforeturns CPU core count, model and load together with total, used and available memory- Streamable HTTP on
/— POST and GET on one route, sessions via theMcp-Session-Idheader, DELETE to end one - Legacy HTTP+SSE on
/ssefor older clients, alongside the new route rather than instead of it - Structured logging with a
component,session_id,method,durationandstatuson every event
Requirements
Go toolchain to build: go build -o system-info-server ., or use the Docker image built from the repo. Running the binary with no arguments gives stdio; setting PORT switches it to HTTP. LOG_LEVEL and ENVIRONMENT control logging — production emits JSON with RFC3339 timestamps, development emits coloured console output. No account, no key, nothing external: it reads the host it runs on.
Setup effort
Build from source — get the source and build it, then follow the project's own run instructions
USE CASES
01
Checking whether a box is under load before you deploy to it
Read CPU model, core count and current load in one call.
02
Explaining why something on the machine got slow
Pull memory totals — used against available — alongside CPU load.
03
Giving a remote agent a health signal
Run it over Streamable HTTP behind a proxy and query it from wherever the agent lives.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
INSTALLATION
Connect your client
Server setup
TERMINAL
go build -o system-info-server .MCP Clients
Cursor — Local stdio
CURSOR — LOCAL STDIO · JSON
{
"mcpServers": {
"system-info-local": {
"command": "<YOUR_PATH_TO_SYSTEM_INFO_SERVER>",
"args": []
}
}
}Cursor — Remote HTTP
CURSOR — REMOTE HTTP · JSON
{
"mcpServers": {
"system-info-remote": {
"url": "<YOUR_SERVER_URL>/"
}
}
}Cursor — SSE
CURSOR — SSE · JSON
{
"mcpServers": {
"system-info-legacy": {
"url": "<YOUR_SERVER_URL>/sse"
}
}
}
