A
licenseA
qualityB
maintenanceEnables AI agents to search, compare, and right-size Hugging Face models, including estimating whether a model fits in available GPU VRAM before downloading it.
5
MIT
vram-mcp
by sushiHex
Related Servers
Alternatives to vram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes NVIDIA GPU metrics (info, utilization, VRAM, temperature) via MCP tools for real-time querying from AI assistants.5MIT
- AlicenseAqualityCmaintenanceEnables AI agents to search Vast.ai GPU marketplace, deploy compute-heavy video models or ComfyUI, and guarantee instances are torn down after the job finishes.172MIT
gpu.nz MCP serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to search live GPU offers, estimate model VRAM, rent and monitor cloud GPU servers with ready templates, read logs, and stop or destroy them when done. Browsing and VRAM estimates work without an API key, while server management requires one.1MIT- AlicenseBqualityDmaintenanceEnables complete local Ollama management including listing models, chatting with local LLMs, starting/stopping the server, and getting intelligent model recommendations for specific tasks through natural language commands.94MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage LM Studio models, including listing, loading, and unloading models through the LM Studio API.616 npm5ISC
TDQS
A3.6/5.0
Scored across 13 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but there is real overlap between list_loaded and vram_status (both report residency) and between history and trend (both surface historical data). The descriptions do enough to separate them, so an agent can mostly disambiguate, but these pairs require reading carefully.
Naming Consistency3/5
There is a discernible pattern — verb_noun for actions (list_loaded, ensure_free, list_claims) and bare verbs for mutations (unload, warm, renew, release) — but query tools use bare nouns (history, trend, advise, claim, reserve), mixing conventions. It is readable but not a single predictable scheme.
Tool Count5/5
13 tools is well-scoped for VRAM lifecycle management: monitoring, eviction/loading, and a cooperative claim/reservation system. Each tool earns its place without redundancy or padding.
Completeness4/5
The claim lifecycle is complete (claim/renew/release/list_claims) and monitoring covers status, history, trend, and advice. Minor gap: reservations (reserve) lack an explicit release/list counterpart, so non-Ollama capacity reservations may be harder to inspect or cancel.
Maintenance
ActivityMaintained
ResponsivenessWithin a week