GPU Server MCP server
io.github.moezdil/mcp-gpu-server·v0.2.2MCP server for GPU monitoring: nvidia-smi, VRAM, utilization, temperature
0 stars235 downloads/wk
Reviews
Write oneNobody has reviewed GPU Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
GPU Server tools (5)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
gpu_infoGPU name, driver version, and CUDA version for each device.
gpu_statsFull snapshot: info, VRAM, utilization, and temperature for every device.
gpu_temperatureCore temperature in °C for each device.
gpu_utilizationGPU core and memory utilization percentage for each device.
gpu_vramVRAM total, used, free (MiB) and utilization % for each device.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How GPU Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 235
- more than 77% of 12,191 servers with a package
What its tools let an agent do: 5 read
Install GPU Server in Claude Code, Cursor or VS Code
claude mcp add mcp-gpu-server -- uvx gpu-server
What the publisher says
From the GPU Server repository's README, as published. We do not edit it. Read it on GitHub
mcp-name: io.github.moezdil/mcp-gpu-server
mcp-gpu-server
An MCP server that exposes NVIDIA GPU metrics as tools. Once connected, any MCP-compatible client can query your GPU status in real time directly from a conversation.
What it does
Instead of running nvidia-smi manually, you ask your AI assistant and it calls these tools automatically:
gpuinfo GPU name, driver version, CUDA version gpuutilization core utilization % and memory controller busy % gpuvram total, used, free VRAM in MiB and usage % gputemperature GPU core temperature in Celsius gpu_stats everything above in one call
Example response from gpu_stats:
{ "count": 1, "gpus": [{ "index": 0, "name": "NVIDIA L40S", "driver": "580.126.09", "cuda": "13.0", "tempc": 29, "gpupct": 0, "mempct": 0, "vram": { "totalmib": 46068, "usedmib": 610, "freemib": 45457, "pct": 1.3 } }] }
How it works
Queries NVML (pynvml) directly when available. Falls back to nvidia-smi subprocess if NVML is not accessible. Returns clean JSON in both cases. The nvidia-smi query does not include the CUDA version, so cuda is null on that path.
Install
pip install gpu-server
The package moved from mcp-gpu-server to gpu-server on PyPI in 0.2.1. The old name is frozen at 0.1.3, which does not start with mcp 2.x. The mcp-gpu-server command still works, and since 0.2.2 gpu-server does too.
Listed on the official MCP Registry as io.github.moezdil/mcp-gpu-server.
Connect to your MCP client
Add this to your MCP client config file:
{ "mcpServers": { "gpu": { "command": "mcp-gpu-server" } } }
Or without installing anything, using uv:
{ "mcpServers": { "gpu": { "command": "uvx", "args": ["gpu-server"] } } }
Run tests
uv run pytest tests/testserver.py # no GPU needed uv run python tests/testgpu.py # on a GPU host
Tested on real hardware
Release 0.2.2 was installed from PyPI into a clean virtual environment on a Linux host and tested against a real GPU on 2026-10-21.
Install the published package and run the GPU integration test:
python3 -m venv venv venv/bin/pip install gpu-server==0.2.2 git clone --depth 1 https://github.com/moezdil/mcp-gpu-server.git repo venv/bin/python repo/tests/test_gpu.py
Result: all 37 checks passed. They exercise the NVML path; the nvidia-smi fallback is only checked for presence, not parsed.
Then call every tool through a real MCP client over stdio:
import anyio, json, sys from mcp import Client, StdioServerParameters
async def main(): async with Client(StdioServerParameters(command=sys.argv[1])) as c: print("protocol:", c.protocolversion) for t in (await c.listtools()).tools: r = await c.calltool(t.name, {}) print(t.name, t.annotations.readonlyhint, json.dumps(r.structuredcontent))
anyio.run(main)
Saved as e2e.py and run with venv/bin/python e2e.py venv/bin/gpu-server. Result: the client and server negotiated protocol 2026-07-28, all five tools are listed as read-only, and every call returned structured content without errors:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
GPU Server: common questions
- Is GPU Server MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the GPU Server safety report
- How do I install GPU Server?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does GPU Server need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is GPU Server maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.2.2.
- How does GPU Server compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.