
GPU Server
io.github.mesutoezdilPublished by GitHub account mesutoezdilv0.1.3Updated Nov 3, 2026
MCP server for GPU monitoring: nvidia-smi, VRAM, utilization, temperature
Overview
Local MCP server that exposes NVIDIA GPU metrics — name, driver, CUDA, utilization, VRAM and temperature — as read-only tools for an assistant.
- What you can do
- Read GPU identity and driver/CUDA versions
- Check core utilization and memory controller busy percentage
- Report total, used and free VRAM in MiB with usage percentage
- Read GPU core temperature in Celsius
- Fetch all of the above in a single combined call
- When to use it
- Useful when you want to ask an assistant about the state of the GPU on the machine it runs on — checking VRAM headroom before loading a model, watching utilization or temperature during a workload — instead of running nvidia-smi by hand.
- Requirements
- Runs locally over stdio as a Python package (pip install gpu-server, or uvx gpu-server without installing). Needs Python 3.10 or higher, the MCP Python SDK 2.x, and an NVIDIA GPU with drivers installed on the host; it queries NVML and falls back to nvidia-smi. No accounts, keys or environment variables are declared.
Installation
In SourceWeft
- Open GPU Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
Example response from gpu_stats:
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
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:
Or without installing anything, using uv:
Run tests
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:
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:
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:
Requirements
Python 3.10 or higher, MCP Python SDK 2.x. NVIDIA GPU with drivers installed on the host machine.
Links
- PyPI: https://pypi.org/project/gpu-server/
- MCP Registry entry: https://registry.modelcontextprotocol.io/v0/servers?search=io.github.moezdil/mcp-gpu-server
- Model Context Protocol: https://modelcontextprotocol.io
- MCP Python SDK: https://github.com/modelcontextprotocol/python-sdk
- uv: https://docs.astral.sh/uv/
- NVML (nvidia-ml-py): https://pypi.org/project/nvidia-ml-py/
Source: README.md at commit a52bdcf
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.